Re: About GIT and committing submissions

On Mon, 18 Oct 2021, Greg 'groggy' Lehey wrote: I'm relatively neutral about this, but if it's adopted, please document it. git still seems like a minefield to me. Lots of references to "git hell" etc... It's basically a terrible design. I use BitKeeper for my internal stuff; it helps that

Re: About GIT and committing submissions

* Greg 'groggy' Lehey [20211018 15:26]: > I'm relatively neutral about this, but if it's adopted, please > document it. That's a good idea of course. Document just the "standard" workflow, so everyone involved (contributors and committers) have a nice "quick start". I think it could make everyone

Re: About GIT and committing submissions

On Saturday, 16 October 2021 at 13:29:34 +0200, Felix Palmen wrote: > > In order to make this more consistent, I'd suggest a few additional > guidelines: ... > I'm relatively neutral about this, but if it's adopted, please document it. git still seems like a minefield to me. Greg -- Sent from my

Re: About GIT and committing submissions

* Miroslav Lachman <000.f...@quip.cz> [20211016 21:15]: > Please keep shar and classic diff patches supported. Git is not the only > tool for everybody on this planet. I don't think it makes too much sense to put them into the same sentence. As for me (see my original mail), I really think any pat

Re: About GIT and committing submissions

On 16/10/2021 15:55, Robert Clausecker wrote: Hi Felix, Using diff -r to make patches works, too. I used to do stuff like this: cd /usr/ports cp -r foo/bar foo/bar.orig ... hack hack hack ... diff -r foo/bar.orig foo/bar and it worked fine for making patches against the po

Re: About GIT and committing submissions

Hi Felix, Using diff -r to make patches works, too. I used to do stuff like this: cd /usr/ports cp -r foo/bar foo/bar.orig ... hack hack hack ... diff -r foo/bar.orig foo/bar and it worked fine for making patches against the ports tree (unless files were added or deleted). The

Different list addresses? (was: About GIT and committing submissions)

Unrelated side note: The mail I was replying to had no Mail-Followup-To header, but it had these: List-Id: Porting software to FreeBSD List-Post: It seems this caused my MUA (neomutt) to direct the followup to *both* addresses. Is there a problem with the mailing-list

Re: About GIT and committing submissions

* Robert Clausecker [20211016 14:11]: > However, I would like to keep the shar guidelines. Submitting a port as a > shar is a very simple way to do so if you have not set up a complete > development environment with git. If you don't have your ports tree under > git, it is difficult to produce a

Re: About GIT and committing submissions

Hi, I support your proposed guidelines for using git. However, I would like to keep the shar guidelines. Submitting a port as a shar is a very simple way to do so if you have not set up a complete development environment with git. If you don't have your ports tree under git, it is difficult to

About GIT and committing submissions

Hi all, since the transition to GIT, there's a way to have author information of a commit in the VCS' own metadata, so the commit message metadata field 'Submitted by:' shouldn't be used any more. But in practice, I see a nice mixture of * Using GIT's --author info * Using 'Submitted by:' * Even