Mailing-List: contact dev-help@corinthia.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@corinthia.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <E467F344-D6EF-4163-9BC2-EFA350E72EFF@apache.org>
References: <75cba8b43a894126b052c2449c2127cb@git.apache.org>
	<937393F8-0857-42DE-9C5C-86A78E9B74B1@apache.org>
	<00cd01d0d328$3bcc6d30$b3654790$@acm.org>
	<259FC673-2A75-44F9-BE85-036287214C46@apache.org>
	<E467F344-D6EF-4163-9BC2-EFA350E72EFF@apache.org>
Date: Mon, 10 Aug 2015 09:12:20 +0200
Message-ID: 
 <CAK2iWdQLHegm4A2mCPJ8CUMG4Em_1pDFbxBCQjxjn0tFs5+itw@mail.gmail.com>
Subject: Re: incubator-corinthia git commit: 0.07 .gitignore clean-up
From: jan i <jani@apache.org>
To: "dev@corinthia.incubator.apache.org" <dev@corinthia.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a1136cbd8e249dc051cefb491

--001a1136cbd8e249dc051cefb491
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Monday, August 10, 2015, Peter Kelly <pmkelly@apache.org> wrote:

> Also one other point I forgot to mention about history for releases - thi=
s
> is available from the git repository for anyone who wants it, by going to
> the tag/branch for that particular release.
>
> Many projects include a ChangeLog file in their release with a summary of
> what=E2=80=99s changed (though not as detailed as individual files or a c=
omplete
> git log). I think ChangeLog files make sense on a per-release basis, then
> people can use that as a guide if they want to go into the git log and se=
e
> all the details.

+1 a ChangeLog file as a simple git log extract makes sense.


>
> =E2=80=94
> Dr Peter M. Kelly
> pmkelly@apache.org <javascript:;>
>
> PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key=
>
> (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
>
> > On 10 Aug 2015, at 1:55 pm, Peter Kelly <pmkelly@apache.org
> <javascript:;>> wrote:
> >
> >> On 10 Aug 2015, at 11:51 am, Dennis E. Hamilton <
> dennis.hamilton@acm.org <javascript:;>> wrote:
> >>
> >> I do that because source tarballs of release code don't have history.
> Just a historical habit.
> >>
> >> Also, when I crib a file to a different project, likewise.
> >>
> >> Does it bother you so much that you don't want to see that kind of
> thing from me?
> >
> > It=E2=80=99s not a major problem if it=E2=80=99s only a few config file=
s here and there
> like .gitignore. But I would not want to see it in source files. Looking =
at
> the git log, we have a very extensive history of changes, and including t=
he
> commit messages (or even summaries) in every file would make them
> considerably larger. It also complicates merging.

I agree with you it would blow up the source for no reason, good argument.


> >
> > My preference is that we use git in the way it=E2=80=99s designed to be=
 used,
> instead of a roll-your-own log system in individual files (esp. when many
> changes span multiple files). I don=E2=80=99t think I=E2=80=99ve ever see=
n anyone else do
> this in a project which already uses a version control system.

+1 it is mandatory that we keep the info in the version control system, the
other can only be extra.

I have seen a couple of projects that (somehow) get the git message
automatically inserted in the source, not something I like.

rgds
jan i

> >
> > =E2=80=94
> > Dr Peter M. Kelly
> > pmkelly@apache.org <javascript:;>
> >
> > PGP key: http://www.kellypmk.net/pgp-key <
> http://www.kellypmk.net/pgp-key>
> > (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
> >
>
>

--=20
Sent from My iPad, sorry for any misspellings.

--001a1136cbd8e249dc051cefb491--