From: Junio C Hamano <firstname.lastname@example.org> To: Ed Hutchins <email@example.com> Cc: Antoine Pelisse <firstname.lastname@example.org>, git <email@example.com> Subject: Re: Feature request: "author branch" in commit object Date: Wed, 03 Jul 2013 11:19:57 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CADL+T9bbnGSxCjUBqoL3qm7Ss-j9jxorED0L1A6v1NbeLBpRQg@mail.gmail.com> (Ed Hutchins's message of "Wed, 3 Jul 2013 10:31:51 -0700") Ed Hutchins <email@example.com> writes: > I might be able to switch our corporate workflow to adding non-ff merge > commits, but the reason we moved away from using github's big red button > in the first place was to avoid the extra noise of merge-only commits. > > Actually you've pointed out an inconsistency: why is it okay for merge > commits to automatically mention branch names, but for regular commits > this is considered harmful? We do not care what you write as part of human-readable payload. Your local convention could be to add, near the end of your log messages, "Made-on-branch: frotz" line, just like all the commits in our project have "Signed-off-by: line" at the end. The problem we avoid is to add it as structural part of the commit object.
next prev parent reply other threads:[~2013-07-03 18:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-02 19:37 Ed Hutchins 2013-07-02 19:49 ` Fredrik Gustafsson 2013-07-02 20:00 ` Junio C Hamano 2013-07-02 20:34 ` Ed Hutchins 2013-07-03 16:16 ` Antoine Pelisse 2013-07-03 17:31 ` Ed Hutchins 2013-07-03 18:19 ` Junio C Hamano [this message] 2013-07-04 0:00 ` Andrew Ardill 2013-07-02 20:31 ` Johan Herland 2013-07-03 9:33 ` Matthieu Moy 2013-07-03 15:47 ` Ed Hutchins 2013-07-03 18:08 ` Junio C Hamano 2013-07-03 23:46 ` Feature request: Jakub Narebski 2013-07-03 23:52 ` Dany 2013-07-03 23:53 ` Dany 2013-07-04 8:08 ` Matthieu Moy 2013-07-09 21:46 ` Feature request: "author branch" in commit object Philip Oakley
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Feature request: "author branch" in commit object' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).