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

Re: [PATCH] filter-branch: rewrite only refs which were not excluded bythe options

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 24, 2007, 11:33 UTC
Message-ID
<Pine.LNX.4.64.0707241229170.14781@racer.site>
In-Reply-To
<46A5E136.D413D3B7@eudaptics.com>
Hi,
On Tue, 24 Jul 2007, Johannes Sixt wrote:
Show 12 quoted lines
> Johannes Schindelin wrote:
> > So really exclude excluded refs from being rewritten.  This also allows
> > you to safely call
> > 
> >         git filter-branch <some-filter> --all <rev-list options>
> > 
> > to rewrite _all_ branches and tags.
> 
> BTW, '--all' in the argument list of filter-branch works only if it is
> preceded by '--':
> 
> 	git filter-branch <some-filter> -- --all <rev-list options>
Hmm.  Maybe we should reconsider the logic.  I.e. instead of
        *)
                usage
        *)
                break
Show 31 quoted lines
> > @@ -181,6 +181,7 @@ export GIT_DIR GIT_WORK_TREE=.
> > 
> >  # These refs should be updated if their heads were rewritten
> > 
> > +negatives="$(git rev-parse --revs-only "$@" | grep "^\^")"
> >  git rev-parse --revs-only --symbolic "$@" |
> >  while read ref
> >  do
> > @@ -196,7 +197,13 @@ do
> >                         grep "refs/\(tags\|heads\)/$ref$")"
> >         esac
> > 
> > -       git check-ref-format "$ref" && echo "$ref"
> > +       # make sure we have a valid ref
> > +       git check-ref-format "$ref" || continue
> > +
> > +       # if the ref has been excluded by the other options, skip it
> > +       test -z "$(git rev-list -1 "$ref" $negatives)" && continue
> 
> Does this catch my use-case with --since? I think not, because:
> 
> $ git rev-parse --revs-only --since=2007.01.01 master topic
> --max-age=1167606000
> 257061f3323dc0162f731d934f0870e919211fdf
> 3405729b94a654df8afbb9a1e13a4cf49a1c351c
> 
> There are no negatives. Does it help to filter the non-positives?
> 
> negatives=$(git rev-parse --revs-only "$@" | egrep -v '^[0-9a-f]{40}$')
> 
> (Except the the '{40}' part is not portable. Hmpf.)

To keep the "--since=..." we have to lose the "--revs-only"... Darn. I thought that "--since=" was expanded by rev-parse. FWIW this might work:

negatives="$(git rev-parse "$@" | while read line
	do
		case "$line" in
		$_x40) ;;
		*) echo "$line";;
		esac
	done)"
Can you please test?  I am off for lunch.

Ciao, Dscho

Previous: Johannes SixtNext: Johannes Sixt
Message 11 of 20 in “filter-branch: Big syntax change; support rewriting multiple refs”
  1. filter-branch: Big syntax change; support rewriting multiple refsJohannes Schindelin, Jul 23, 2007
  2. Junio C HamanoJul 24, 2007
  3. Johannes SchindelinJul 24, 2007
  4. Johannes SixtJul 24, 2007
  5. filter-branch: when dwim'ing a ref, only allow heads and tagsJohannes Schindelin, Jul 24, 2007
  6. Johannes SixtJul 24, 2007
  7. Johannes SchindelinJul 24, 2007
  8. filter-branch: when dwim'ing a ref, only allow heads and tagsJohannes Schindelin, Jul 24, 2007
  9. filter-branch: rewrite only refs which were not excluded by the optionsJohannes Schindelin, Jul 24, 2007
  10. Johannes SixtJul 24, 2007
  11. Johannes SchindelinJul 24, 2007
  12. Johannes SixtJul 24, 2007
  13. Johannes SchindelinJul 24, 2007
  14. Johannes SixtJul 24, 2007
  15. Johannes SchindelinJul 24, 2007
  16. Johannes SixtJul 24, 2007
  17. Johannes SchindelinJul 24, 2007
  18. filter-branch: rewrite only unexcluded refsJohannes Schindelin, Jul 24, 2007
  19. Johannes SixtJul 24, 2007
  20. Johannes SchindelinJul 24, 2007

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.