git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Feature request: "author branch" in commit object

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
Jul 4, 2013, 00:00 UTC
Message-ID
<CAH5451kq-zmy1kFFqx44ba4iM+H4zCF2J3GMc2ppcmoz5=urXA@mail.gmail.com>
In-Reply-To
<7vli5nfquq.fsf@alter.siamese.dyndns.org>
On 4 July 2013 09:46, Jakub Narebski <jnareb@gmail.com> wrote:
Show 9 quoted lines
> Junio C Hamano <gitster <at> pobox.com> writes:
>> It is not just misleading but is actively wrong to recording the
>> name of the original branch in commits and carrying them forward via
>> rebase. If you want a record of what a group of commits were about,
>> the right time to do so is when you merge.
>
> There is even git-resurrect.sh script in 'contrib/' that makes
> use of that practice to find merged-in and deleted branches,
> and resurrect them (among other tools).

How do users who wish to keep a record of branch names find out that --no-ff will enable this behaviour?

Is this a common enough requirement to make --no-ff the default behaviour (probably not, and that transition would be painful)?

What are the shortcomings of using --no-ff in the analogue to how mercurials named branches work?

I think the git-flow and git-list style workflows have done a lot to promote a set of usage patterns that keep this metadata around, I just wonder if we can do more to assist users in what seems to be a relatively common request.

Regards,
Andrew Ardill
Previous: Junio C HamanoNext: Johan Herland
Message 8 of 17 in “Feature request: "author branch" in commit object”
  1. Ed HutchinsJul 2, 2013
  2. Fredrik GustafssonJul 2, 2013
  3. Junio C HamanoJul 2, 2013
  4. Ed HutchinsJul 2, 2013
  5. Antoine PelisseJul 3, 2013
  6. Ed HutchinsJul 3, 2013
  7. Junio C HamanoJul 3, 2013
  8. Andrew ArdillJul 4, 2013
  9. Johan HerlandJul 2, 2013
  10. Matthieu MoyJul 3, 2013
  11. Ed HutchinsJul 3, 2013
  12. Junio C HamanoJul 3, 2013
  13. Jakub NarebskiJul 3, 2013
  14. DanyJul 3, 2013
  15. DanyJul 3, 2013
  16. Matthieu MoyJul 4, 2013
  17. Philip OakleyJul 9, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.