From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Binutils Development <binutils@sourceware.org>,
GDB Development <gdb@sourceware.org>
Subject: Re: src.git test repository
Date: Thu, 10 Oct 2013 13:22:00 -0000 [thread overview]
Message-ID: <87eh7t9s6s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20131010051314.GI3066@adacore.com> (Joel Brobecker's message of "Thu, 10 Oct 2013 09:13:14 +0400")
Joel> There will be issues with special-feature development branches, however.
Joel> Let's say, for instance, that people want to collaborate on a certain
Joel> feature, and use a branch for its development. If development takes
Joel> a while, they might want to do regular merges from HEAD... We can adjust
Joel> the rule to say that merges are verbotten except on branches whose name
Joel> is prefixed by Eg. "topic/".
Perhaps just prohibiting them on master is enough?
Joel> - we seem to be getting one email per push, instead of one email
Joel> per commit?
I checked, and yeah, this is what happens.
I think I can change that, if you want.
Joel> - Style check the revision log to forbid commits if the second
Joel> line (line after subject) is not empty. I have found that
Joel> this assumption is too ingrained everywhere in git, and that
Joel> not respecting it makes things look bad.
While I agree that we ought to adopt a more git-ish commit style, this
goes against my early plan of making as few "extra" change to our
processes as possible. I was leaving all non-essential change proposals
for later, to avoid complicating the switchover.
I guess if enough people +1 the idea I will do it.
Tom
next prev parent reply other threads:[~2013-10-10 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 15:19 Tom Tromey
2013-10-07 16:24 ` Eli Zaretskii
2013-10-07 16:53 ` Tom Tromey
2013-10-07 16:43 ` H.J. Lu
2013-10-07 16:56 ` Tom Tromey
2013-10-08 23:28 ` Iain Sandoe
2013-10-09 1:29 ` Tom Tromey
2013-10-09 5:15 ` Iain Sandoe
2013-10-09 21:04 ` Tom Tromey
2013-10-10 5:13 ` Joel Brobecker
2013-10-10 13:22 ` Tom Tromey [this message]
2013-10-10 13:44 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eh7t9s6s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox