From: Tom Tromey <tromey@redhat.com>
To: Binutils Development <binutils@sourceware.org>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: src.git test repository
Date: Wed, 09 Oct 2013 21:04:00 -0000 [thread overview]
Message-ID: <87r4bu9mw3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87y565m7ma.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 07 Oct 2013 09:19:09 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> I've made a src.git test repository for testing. Please try it out.
Tom> This repository has all the configuration bits in it that I expect to
Tom> use in the final conversion -- email hooks, bugzilla hooks, etc. Please
Tom> be aware of that if you make any changes.
One note here is that I am still considering a hook to reject merge
commits.
The rationale for this is that merge commits are ugly, and that it isn't
a big deal to require a rebase before a merge, so that any merge is a
fast-forward.
I think it isn't onerous to follow this rule for all branches -- there
being plenty of options for git hosting where you can go nuts -- but of
course I welcome your considered reasons to think otherwise.
Tom> (I intend to test all these things live sometime this week. So far
Tom> they've only been tested piecemeal on my machine.)
I've done various test commits and pushes and I think these scripts are
working adequately well.
If you want to see the current format of the commit messages, look at
one of the "cvs" mailing lists. E.g.:
https://sourceware.org/ml/gdb-cvs/2013-10/msg00062.html
We can make changes to the format if desired. I tried to keep pretty
much the same information that was in the old CVS commit message, though
I didn't attempt to exactly mimic the format.
Commits mentioning PRs also go to bugzilla. See my test PR for an
example:
https://sourceware.org/bugzilla/show_bug.cgi?id=16030
The format for bugzilla can differ from the format for the commit-list
message, but I chose to keep them the same. Again, changeable.
Tom
next prev parent reply other threads:[~2013-10-09 21:04 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 [this message]
2013-10-10 5:13 ` Joel Brobecker
2013-10-10 13:22 ` Tom Tromey
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=87r4bu9mw3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=binutils@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).