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

Re: [PATCH] disable grafts during fetch/push/bundle

From
Christian Couder <christian.couder@gmail.com>
Date
Mar 7, 2014, 07:08 UTC
Message-ID
<CAP8UFD0UnUGZb9hWyLS1vPJ6fh3QR-g_p5HNQk79Gqhs9YWi0A@mail.gmail.com>
In-Reply-To
<xmqqob1ivqv4.fsf@gitster.dls.corp.google.com>
On Fri, Mar 7, 2014 at 12:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 25 quoted lines
> Michael Haggerty <mhagger@alum.mit.edu> writes:
>
>> I didn't mean to insult all Windows users in general.  I was only
>> referring to the fact that since the default Windows command line is not
>> a POSIX shell, even an experienced Windows user might have trouble
>> figuring out how to execute a shell loop.  Putting this functionality in
>> a git command or script, by contrast, would make it work universally, no
>> fuss, no muss.
>
> ;-)
>
> Be it graft or replace, I do not think we want to invite people to
> use these mechansims too lightly to locally rewrite their history
> willy-nilly without fixing their mistakes at the object layer with
> "commit --amend", "rebase", "bfg", etc. in the longer term.  So in
> that sense, adding a command to make it easy is not something I am
> enthusiastic about.
>
> On the other hand, if the user does need to use graft or replace
> (perhaps to prepare for casting the fixed history in stone with
> filter-branch), it would be good to help them avoid making mistakes
> while doing so and tool support may be a way to do so.
>
> So, ... I am of two minds.
>

Maybe if we add a new command (or maybe a script) with a name long and cryptic-looking enough like "git create-replacement-object" it will scare casual users from touching it, while power users will be happy to benefit from it.

Previous: Junio C HamanoNext: Jeff King
Message 25 of 35 in “disable grafts during fetch/push/bundle”
  1. disable grafts during fetch/push/bundleJeff King, Mar 4, 2014
  2. Junio C HamanoMar 4, 2014
  3. Jeff KingMar 5, 2014
  4. Junio C HamanoMar 5, 2014
  5. Jeff KingMar 5, 2014
  6. Junio C HamanoMar 5, 2014
  7. Jeff KingMar 5, 2014
  8. Junio C HamanoMar 5, 2014
  9. Michael HaggertyMar 6, 2014
  10. Christian CouderMar 6, 2014
  11. Jeff KingMar 6, 2014
  12. Michael HaggertyMar 6, 2014
  13. Jeff KingMar 6, 2014
  14. 1/4 replace: refactor command-mode determinationJeff King, Mar 6, 2014
  15. 2/4 replace: use OPT_CMDMODE to handle modesJeff King, Mar 6, 2014
  16. 3/4 replace: factor object resolution out of replace_objectJeff King, Mar 6, 2014
  17. 4/4 replace: add --edit optionJeff King, Mar 6, 2014
  18. Eric SunshineMar 7, 2014
  19. Jeff KingMar 7, 2014
  20. Junio C HamanoMar 6, 2014
  21. Jeff KingMar 6, 2014
  22. Philip OakleyMar 6, 2014
  23. Michael HaggertyMar 6, 2014
  24. Junio C HamanoMar 6, 2014
  25. Christian CouderMar 7, 2014
  26. Jeff KingMar 7, 2014
  27. Junio C HamanoMar 19, 2014
  28. Jeff KingMar 21, 2014
  29. Philip OakleyMar 6, 2014
  30. Eric SunshineMar 4, 2014
  31. Jeff KingMar 5, 2014
  32. Eric SunshineMar 5, 2014
  33. Jeff KingMar 5, 2014
  34. Eric SunshineMar 5, 2014
  35. Jeff KingMar 6, 2014

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.