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

Re: [PATCH] Make git-branch a builtin

From
Shawn Pearce <spearce@spearce.org>
Date
Oct 24, 2006, 05:44 UTC
Message-ID
<20061024054408.GA9724@spearce.org>
In-Reply-To
<7vfydewqbb.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 26 quoted lines
> Shawn Pearce <spearce@spearce.org> writes:
> 
> > Lars Hjemli <hjemli@gmail.com> wrote:
> > [snip]
> >> ---
> >>  Makefile         |    3 +-
> >>  builtin-branch.c |  217 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>  builtin.h        |    1 +
> >>  git-branch.sh    |  131 --------------------------------
> >>  git.c            |    1 +
> >>  5 files changed, 221 insertions(+), 132 deletions(-)
> > [snip]
> >> diff --git a/git-branch.sh b/git-branch.sh
> >> deleted file mode 100755
> >> index 4379a07..0000000
> >> --- a/git-branch.sh
> >> +++ /dev/null
> >> @@ -1,131 +0,0 @@
> > [snip 131 lines]
> >
> > Aside from compatability with non-Git tools...
> >
> > Wouldn't it make more sense to just include the full SHA1 of the
> > file we are deleting rather than the entire 131 line negative diff?
> 
> How would you do "git apply -R" on something like that?

Uh, you have the full SHA1 in the index line. So you just have to reattach that blob to the named path... pretty simple actually.

Of course this is yet another code path in apply and as Petr pointed out on this same thread its nice to know what you are deleting so you can compare it to what else is changing in the same patch... so this suggestion of mine is probably just a waste of bytes.

-- 
Shawn.
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 11 in “Make git-branch a builtin”
  1. Make git-branch a builtinLars Hjemli, Oct 23, 2006
  2. Shawn PearceOct 23, 2006
  3. Petr BaudisOct 23, 2006
  4. Junio C HamanoOct 23, 2006
  5. Shawn PearceOct 24, 2006
  6. Junio C HamanoOct 24, 2006
  7. Shawn PearceOct 24, 2006
  8. Petr BaudisOct 24, 2006
  9. Junio C HamanoOct 24, 2006
  10. Junio C HamanoOct 23, 2006
  11. Git-branch: fix regression and style issuesLars Hjemli, Oct 23, 2006

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.