* Re: combine git repo historically
From: bill lam @ 2009-10-10 14:03 UTC (permalink / raw)
To: Johannes Sixt; +Cc: git, Christian Couder
In-Reply-To: <4ACED204.3000907@viscovery.net>
On Fri, 09 Oct 2009, Johannes Sixt wrote:
> bill lam schrieb:
> > I have two git repos, no branches.
> >
> > repo 1.
> > emptyrootcommit -- A ... M
> >
> > repo 2.
> > emptyrootcommit -- N ... Z
> >
> > N was evolved from M but the time gap is large, how can I combine them
> > into one repo
> >
> > emptyrootcommit -- A ... M -- N ... Z
> >
> > so that snapshots N .. Z will not be changed.
>
> $ echo $(git rev-parse N) $(git rev-parse M) >> .git/info/grafts
> $ git filter-branch --tag-name-filter cat -- --all --not M
>
> i.e. you graft the older history right before the younger history, then
> you use git filter-branch to rewrite the parentship of the younger commits.
Thanks, graft is new to me. I tested it works but it needs first issue
git fetch /path/to/repo1
within repo2 to fetch tip M from repo1 into repo2, is it correct?
If I also want to fetch also all objects from repo1, what will the
command to do it.
Christian Couder also mentioned the git-replace command, how to stitch
with it?
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
^ permalink raw reply
* Re: [PATCH 1/2] t/test-lib.sh: support Korn shell by converting GIT_EXIT_OK to GIT_EXIT_CODE
From: Jeff King @ 2009-10-10 14:03 UTC (permalink / raw)
To: Ben Walton; +Cc: Andreas Schwab, GIT List
In-Reply-To: <1255178966-sup-5813@ntdws12.chass.utoronto.ca>
On Sat, Oct 10, 2009 at 08:53:00AM -0400, Ben Walton wrote:
> > According to the autoconf docs this bug is also present in the Solaris
> > /bin/sh (and autoconf generated scripts use some elaborated workaround).
>
> Solaris' /bin/sh shouldn't be used for anything but forking a decent
> shell, imo. It was brought to my attention recently that the test
> suite for mercurial on solaris was failing the git tests. The
> mercurial folks initially thought this was a git on solaris bug.
Yes, that is the attitude we take towards /bin/sh on Solaris. Most
people running git on Solaris (or other broken-shell platforms) point
SHELL_PATH to bash. I think the point of Brandon's patch is to let them
use a native shell.
So while /bin/sh is broken, the question is whether the alternate native
shell is broken enough to use or not.
-Peff
^ permalink raw reply
* Re: [PATCH 1/2] t/test-lib.sh: support Korn shell by converting GIT_EXIT_OK to GIT_EXIT_CODE
From: Ben Walton @ 2009-10-10 12:53 UTC (permalink / raw)
To: Andreas Schwab; +Cc: GIT List
In-Reply-To: <m2eipbphbr.fsf@igel.home>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Excerpts from Andreas Schwab's message of Sat Oct 10 08:24:40 -0400 2009:
> According to the autoconf docs this bug is also present in the Solaris
> /bin/sh (and autoconf generated scripts use some elaborated workaround).
Solaris' /bin/sh shouldn't be used for anything but forking a decent
shell, imo. It was brought to my attention recently that the test
suite for mercurial on solaris was failing the git tests. The
mercurial folks initially thought this was a git on solaris bug.
After looking into it, I discovered that ^ is still treated[1] as a
pipe symbol[2] in some cases. So, test suite programs run under
/bin/sh on solaris with commands like `git reset --hard HEAD^` were
misbehaving due to the shell setting up a pipeline under the right
circumstances.
-Ben
[1] http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/sh/cmd.c
line 184
[2] This dates back to the Thomson shell:
http://en.wikipedia.org/wiki/Thompson_shell
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: [PATCH 1/2] t/test-lib.sh: support Korn shell by converting GIT_EXIT_OK to GIT_EXIT_CODE
From: Andreas Schwab @ 2009-10-10 12:24 UTC (permalink / raw)
To: Clemens Buchacher; +Cc: Brandon Casey, git, peff, Brandon Casey
In-Reply-To: <20091010120121.GA16336@localhost>
Clemens Buchacher <drizzd@aon.at> writes:
> Hi,
>
> On Fri, Oct 09, 2009 at 01:39:56PM -0500, Brandon Casey wrote:
>
>> For the Korn shell, $? has the value of the last executed statement
>> _before_ the call to exit.
>
> I just installed ksh/stable (version 93s+ 2008-01-31) on Debian and it
> behaves correctly. Maybe you need to upgrade? This really looks like a bug
> in your shell to me.
According to the autoconf docs this bug is also present in the Solaris
/bin/sh (and autoconf generated scripts use some elaborated workaround).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply
* Re: [RFC PATCH 1/4] Document the HTTP transport protocol
From: Tay Ray Chuan @ 2009-10-10 12:17 UTC (permalink / raw)
To: Shawn O. Pearce; +Cc: git
In-Reply-To: <1255065768-10428-2-git-send-email-spearce@spearce.org>
Hi,
On Fri, Oct 9, 2009 at 1:22 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> +Smart Clients
> +~~~~~~~~~~~~~
> +
> +HTTP clients that support the "smart" protocol (or both the
> +"smart" and "dumb" protocols) MUST discover references by making
> +a paramterized request for the info/refs file of the repository.
s/paramterized/parameterized/ -- missing 'e'.
--
Cheers,
Ray Chuan
^ permalink raw reply
* Re: [PATCH 1/2] t/test-lib.sh: support Korn shell by converting GIT_EXIT_OK to GIT_EXIT_CODE
From: Clemens Buchacher @ 2009-10-10 12:01 UTC (permalink / raw)
To: Brandon Casey; +Cc: git, peff, Brandon Casey
In-Reply-To: <1eweIwf5YoFwmLPWwEFN69a2f-EUnj_kgiagVJoVQYfNQeLjlpm12U84RKxhzjh0NJv36SqO12lAX2c_x0WSgA@cipher.nrlssc.navy.mil>
Hi,
On Fri, Oct 09, 2009 at 01:39:56PM -0500, Brandon Casey wrote:
> For the Korn shell, $? has the value of the last executed statement
> _before_ the call to exit.
I just installed ksh/stable (version 93s+ 2008-01-31) on Debian and it
behaves correctly. Maybe you need to upgrade? This really looks like a bug
in your shell to me.
> die () {
> code=$?
> - if test -n "$GIT_EXIT_OK"
> + if test -n "$GIT_EXIT_CODE"
> then
> - exit $code
> + exit $GIT_EXIT_CODE
> else
> echo >&5 "FATAL: Unexpected exit with code $code"
> exit 1
> fi
> }
So in your shell an unexpected exit will always output this?
FATAL: Unexpected exit with code <some command>
If we can't rely on the value of $?, we should not use it.
Clemens
^ permalink raw reply
* Re: Git 1.6.5-rc git clone unhandled exception using http protocol
From: Tay Ray Chuan @ 2009-10-10 10:55 UTC (permalink / raw)
To: eduard stefan; +Cc: Git Mailing List
In-Reply-To: <4ACF7296.3010809@gmail.com>
Hi,
On Sat, Oct 10, 2009 at 1:27 AM, eduard stefan <eduard.stefan@gmail.com> wrote:
> How can I obtain more information about the error?
How are you executing the git commands? From the windows command line?
From the msys bash shell? Could you copy and paste the output of git
when cloning the repo?
How about the win32 exception? What does it say? Does it display as a dialog?
--
Cheers,
Ray Chuan
^ permalink raw reply
* Re: [RFC PATCH 1/4] Document the HTTP transport protocol
From: Antti-Juhani Kaijanaho @ 2009-10-10 10:12 UTC (permalink / raw)
To: git
In-Reply-To: <7vskdss3ei.fsf@alter.siamese.dyndns.org>
On 2009-10-09, Junio C Hamano <gitster@pobox.com> wrote:
>> +If there is no repository at $GIT_URL, the server MUST respond with
>> +the '404 Not Found' HTTP status code.
>
> We may also want to add
>
> If there is no object at $GIT_URL/some/path, the server MUST respond
> with the '404 Not Found' HTTP status code.
>
> to help dumb clients.
In both cases - is it really necessary to forbid the use of 410 (Gone)?
--
Mr. Antti-Juhani Kaijanaho, Jyvaskyla, Finland
^ permalink raw reply
* Re: Merging non-git releases of a project
From: Peter Baumann @ 2009-10-10 10:04 UTC (permalink / raw)
To: Björn Steinbrink; +Cc: Avery Pennarun, Howard Miller, git
In-Reply-To: <20091010090053.GA4843@atjola.homenet>
On Sat, Oct 10, 2009 at 11:00:53AM +0200, Björn Steinbrink wrote:
> On 2009.10.10 10:47:42 +0200, Peter Baumann wrote:
> > On Fri, Oct 09, 2009 at 06:43:50PM -0400, Avery Pennarun wrote:
> > > Try this:
> > >
> > > cd mygitproject
> > > git rm -rf .
> > > cp -a /tmp/wherever/vendor-1.2/. .
> > > git add .
> >
> > This won't commit deleted files from v1.0 - v1.2. Use git add -A to stage all
> > modified and deleted files for the next commit.
>
> It will, the "git rm" already cleans the index.
>
You are right. I missed the "git" part and read only rm -rf.
-Peter
^ permalink raw reply
* git-svn very slow on fetch (shared git-svn repo)
From: Pascal Obry @ 2009-10-10 9:10 UTC (permalink / raw)
To: git list
Here is the problem.
Doing a:
$ git svn fetch
Takes age to update the repository. The long story is that I'm trying to
have shared git-svn repositories.
I'm cloning the repository on a server using a standard "git svn clone".
I then let users cloning this repository using the procedure described
in git-svn help. Copy/paste here:
<<
# Do the initial import on a server
ssh server "cd /pub && git svn clone
http://svn.example.com/project
# Clone locally - make sure the refs/remotes/ space matches the
server
mkdir project
cd project
git init
git remote add origin server:/pub/project
git config --add remote.origin.fetch
'+refs/remotes/*:refs/remotes/*'
git fetch
# Create a local branch from one of the branches just fetched
git checkout -b master FETCH_HEAD
# Initialize 'git svn' locally (be sure to use the same URL and
-T/-b/-t options as were used on server)
git svn init http://svn.example.com/project
# Pull the latest changes from Subversion
git svn rebase
>>
If you do a "git svn fetch" (to get new branches) it takes age if you
have imported branches that are not used since a long time.
I've traced this down to the Perl fetch_all procedure. It seems that the
fetch is looking at the older version in all branches and then read the
remote repository starting from this revision. As some branches are
unused since a very long it it re-read most of the history. In my
example it start at rev 8200 whereas the last revision on trunk is
150000 (I put trace in git-svn Perl script).
I have observed that this happen only the first time.
This can be confirmed by the fact that if you break git-svn fetch
process and restart it it will start to a later revision. So it seems
that git-svn is keeping some kind of data about what has already been
fetched but those data are not properly copied by the procedure above.
Is there a workaround that? Where are those data stored?
Any guidance would be very welcomed.
Thanks,
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net - http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
^ permalink raw reply
* Re: Merging non-git releases of a project
From: Björn Steinbrink @ 2009-10-10 9:00 UTC (permalink / raw)
To: Peter Baumann; +Cc: Avery Pennarun, Howard Miller, git
In-Reply-To: <20091010084742.GB17220@m62s10.vlinux.de>
On 2009.10.10 10:47:42 +0200, Peter Baumann wrote:
> On Fri, Oct 09, 2009 at 06:43:50PM -0400, Avery Pennarun wrote:
> > Try this:
> >
> > cd mygitproject
> > git rm -rf .
> > cp -a /tmp/wherever/vendor-1.2/. .
> > git add .
>
> This won't commit deleted files from v1.0 - v1.2. Use git add -A to stage all
> modified and deleted files for the next commit.
It will, the "git rm" already cleans the index.
Björn
^ permalink raw reply
* Re: Merging non-git releases of a project
From: Howard Miller @ 2009-10-10 8:58 UTC (permalink / raw)
To: Avery Pennarun; +Cc: git
In-Reply-To: <32541b130910091543x19b3b46an109f90be5c5bfaa2@mail.gmail.com>
2009/10/9 Avery Pennarun <apenwarr@gmail.com>:
> On Fri, Oct 9, 2009 at 5:33 PM, Howard Miller
> <howard@e-learndesign.co.uk> wrote:
>> I'm missing the point here though. Where/when do I actually add the
>> new pristine code? If I checkout, as you suggest, my initial commit I
>> just have (say) v1.0 of the vendor's code. I can't just copy (say)
>> version 1.2 on top as the files probably won't match one-one.
>>
>> Sorry - I'm probably completely failing to understand.
>
> Try this:
>
> cd mygitproject
> git rm -rf .
> cp -a /tmp/wherever/vendor-1.2/. .
> git add .
> git commit
>
> Don't worry, git won't double-store files that are identical between
> the old 1.0 and new 1.2 versions.
>
> Avery
>
Adding Unix ignorance to git ignorance... doesn't that delete the .git
directory too?
I don't have cp -a (on a mac) but, IIRC, that's just -rp or somesuch?
But I see, basic idea is to ditch the files, replace them with the new
vendor release a commit. I did think of that but it seemed too simple
:-)
Cheers.
^ permalink raw reply
* Re: Merging non-git releases of a project
From: Peter Baumann @ 2009-10-10 8:47 UTC (permalink / raw)
To: Avery Pennarun; +Cc: Howard Miller, git
In-Reply-To: <32541b130910091543x19b3b46an109f90be5c5bfaa2@mail.gmail.com>
On Fri, Oct 09, 2009 at 06:43:50PM -0400, Avery Pennarun wrote:
> On Fri, Oct 9, 2009 at 5:33 PM, Howard Miller
> <howard@e-learndesign.co.uk> wrote:
> > I'm missing the point here though. Where/when do I actually add the
> > new pristine code? If I checkout, as you suggest, my initial commit I
> > just have (say) v1.0 of the vendor's code. I can't just copy (say)
> > version 1.2 on top as the files probably won't match one-one.
> >
> > Sorry - I'm probably completely failing to understand.
>
> Try this:
>
> cd mygitproject
> git rm -rf .
> cp -a /tmp/wherever/vendor-1.2/. .
> git add .
This won't commit deleted files from v1.0 - v1.2. Use git add -A to stage all
modified and deleted files for the next commit.
> git commit
>
> Don't worry, git won't double-store files that are identical between
> the old 1.0 and new 1.2 versions.
^ permalink raw reply
* Re: [PATCH] git-svn: hide find_parent_branch output in double quiet mode
From: Junio C Hamano @ 2009-10-10 7:02 UTC (permalink / raw)
To: Eric Wong; +Cc: git, Simon Arlott
In-Reply-To: <20091010010843.GA30258@dcvr.yhbt.net>
Eric Wong <normalperson@yhbt.net> writes:
> Thanks Simon,
>
> Acked-by: Eric Wong <normalperson@yhbt.net>
>
> and pushed out to git://git.bogomips.org/git-svn
Thanks; you seem to have rebased the history in this repository, and
merging from you will duplicate Alexander's "Avoid spurious errors", which
I already pulled, so I'll cherry pick this one from your tree.
^ permalink raw reply
* git svn with non-standard svn layout
From: Fabian Molder @ 2009-10-09 22:24 UTC (permalink / raw)
To: git
Hello,
- want to use git inside an huge SVN project
--> so git-svn could do the job ..
- I struggle with two things:
A) - the SVN project has an non-standard layout
B) - want to have (several) git's for just the (few) peaces I work on
for A)
======
- svn layout looks like this (simplified):
- trunk (not really used, all interesting work in branches)
- branches
- r1.2
- development
- integration
- r1.3
- development
- integration
...
- inside development and integration is:
- xapplication1
- xapplication2
- xapplication3
...
- aa
-bb
-cc
- zapplication1
- zapplication2
- zapplication3
...
- I created an simplified svn test (from scratch; import/repo/workdir)
via this bash-script: http://pastebin.ca/1608231
for B)
======
- the svn repo is very huge, but I'm only interested in these dirs:
xapplication2/
aa/bb/cc/zapplication1
- my objectives:
- have several local git's, just the ones I need:
--> xapplication2/.git
--> aa/bb/cc/zapplication1/.git
I tried to use "git config svn-remote.svn.branches" to do this,
please see in function "do_git_svn" in bash-script - but no success
any hints appreciated
regards,
Fabian
^ permalink raw reply
* Re: [PATCH] git-svn: hide find_parent_branch output in double quiet mode
From: Eric Wong @ 2009-10-10 1:08 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git, Simon Arlott
In-Reply-To: <b01cac406b93d5c67e3ae2e9a7aaa498a52dd9fc@8b5064a13e22126c1b9329f0dc35b8915774b7c3.invalid>
Simon Arlott <simon@fire.lp0.eu> wrote:
> Hide find_parent_branch logging when -qq is specified.
> This eliminates more unnecessary output when run from cron, e.g.:
>
> Found possible branch point:
> http://undernet-ircu.svn.sourceforge.net/svnroot/undernet-ircu/ircu2/trunk =>
> http://undernet-ircu.svn.sourceforge.net/svnroot/undernet-ircu/ircu2/branches/authz,
> 1919
> Found branch parent: (authz) ea061d76aea985dc0208d36fa5e0b2249b698557
> Following parent with do_switch
> Successfully followed parent
>
> Signed-off-by: Simon Arlott <simon@fire.lp0.eu>
Thanks Simon,
Acked-by: Eric Wong <normalperson@yhbt.net>
and pushed out to git://git.bogomips.org/git-svn
--
Eric Wong
^ permalink raw reply
* Re: [PATCH 0/9] Documentation tweaks
From: Junio C Hamano @ 2009-10-10 0:58 UTC (permalink / raw)
To: Jonathan Nieder; +Cc: git
In-Reply-To: <20091009101400.GA16549@progeny.tock>
Jonathan Nieder <jrnieder@gmail.com> writes:
> Here are some small documentation patches that have been sitting in
> my tree for a while. Most important is the first one, which makes it
> easier to find the appropriate options for building documentation
> from source on a new machine.
Thanks.
^ permalink raw reply
* Re: [PATCH] Speedup bash completion loading
From: Junio C Hamano @ 2009-10-10 0:57 UTC (permalink / raw)
To: Shawn O. Pearce; +Cc: Kirill Smelkov, Ted Pavlic, git
In-Reply-To: <20091009161443.GX9261@spearce.org>
Thanks for this, and all the other acks and patches.
^ permalink raw reply
* Re: [PATCH 7/9] Documentation: clarify branch creation
From: Junio C Hamano @ 2009-10-10 0:57 UTC (permalink / raw)
To: Jonathan Nieder; +Cc: Sean Estabrooks, git
In-Reply-To: <20091009183408.GB2477@progeny.tock>
Jonathan Nieder <jrnieder@gmail.com> writes:
> So this page should probably point to the what-is-a-branch section of
> the User's Manual. Maybe something like this?
Sounds good. Thanks
> -- %< --
> Subject: Documentation: clarify branch creation
>
> The documentation seems to assume that the starting point for a new
> branch is the tip of an existing (ordinary) branch, but that is not
> the most common case. More often, "git branch" is used to begin
> a branch from a remote-tracking branch, a tag, or an interesting
> commit (e.g. origin/pu^2). Clarify the language so it can apply
> to these cases. Thanks to Sean Estabrooks for the wording.
>
> Also add a pointer to the user's manual for the bewildered.
> ...
^ permalink raw reply
* Re: [PATCH 1/2] t/test-lib.sh: support Korn shell by converting GIT_EXIT_OK to GIT_EXIT_CODE
From: Junio C Hamano @ 2009-10-10 0:57 UTC (permalink / raw)
To: Brandon Casey; +Cc: Brandon Casey, git, drizzd, peff
In-Reply-To: <ee63ef30910091537i40a8cc68y2513f07c91fb35b@mail.gmail.com>
Brandon Casey <drafnel@gmail.com> writes:
> I'm away from a computer right now. Junio, if gmail is showing me the
> entirety of your workaround, then no, I don't think that will work.
> Your code will always exit non-zero, but there are cases where 'exit
> 0' is called and a '0' exit status is desired. e.g. when test_done is
> called.
Ah, of course you are right.
^ permalink raw reply
* Re: [PATCH v2] git-send-email.perl: fold multiple entry "Cc:" and multiple single line "RCPT TO:"s
From: Junio C Hamano @ 2009-10-10 0:57 UTC (permalink / raw)
To: Joe Perches; +Cc: git, Jay Soffian
In-Reply-To: <1255021406.2056.122.camel@Joe-Laptop.home>
This breaks t9001 since it expects an old (and probably incorrect) RCPT TO:
lines. I fixed them up.
^ permalink raw reply
* Re: [PATCH v2 (amend)] gitweb: Do not show 'patch' link for merge commits
From: Junio C Hamano @ 2009-10-10 0:56 UTC (permalink / raw)
To: Jakub Narebski; +Cc: git, Jeff King, Junio Hamano
In-Reply-To: <200910091426.44976.jnareb@gmail.com>
Thanks.
^ permalink raw reply
* Re: [PATCHv4] git-log --format: Add %B tag with %B(n) option
From: Junio C Hamano @ 2009-10-10 0:57 UTC (permalink / raw)
To: Johannes Gilger; +Cc: Git Mailing List, Johannes Schindelin
In-Reply-To: <1253655038-20335-1-git-send-email-heipei@hackvalue.de>
Johannes Gilger <heipei@hackvalue.de> writes:
> diff --git a/pretty.c b/pretty.c
> index f5983f8..dafa8e0 100644
> --- a/pretty.c
> +++ b/pretty.c
> @@ -605,13 +605,17 @@ static size_t format_commit_item(struct strbuf *sb, const char *placeholder,
> int h1, h2;
>
> /* these are independent of the commit */
> +
> + const char *body = msg + c->body_off;
> + const char *end = NULL;
Unfortunately, c->body_off is not valid until you make a call to
parse_commit_message(). Obviously, body is used only after such a call is
made in the original, so I fixed this initialization into an explicit
assignment after the call.
^ permalink raw reply
* Re: [PATCH 1/8] imap-send: remove useless uid code
From: Junio C Hamano @ 2009-10-10 0:57 UTC (permalink / raw)
To: Sverre Rabbelier; +Cc: Erik Faye-Lund, git, gitster, Jeff King, Erik Faye-Lund
In-Reply-To: <fabb9a1e0910090821n67c86d0kb4eef1b9ff4bdff1@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> writes:
> Please include a cover letter for series as long as these (anything
> larger than 4 should have a cover letter IMHO). Doing so makes it
> easier for those that follow the series to see what changed (assuming
> you write down what changed in the cover letter). Also, it makes it
> easier for those that were not following the series to drop in at the
> current version (assuming you provide a short summary of what the
> series is about in the cover letter)..
Thanks.
^ permalink raw reply
* Re: Confusing git pull error message
From: Junio C Hamano @ 2009-10-10 0:57 UTC (permalink / raw)
To: Jeff King; +Cc: Nanako Shiraishi, Johannes Sixt, John Tapsell, Git List
In-Reply-To: <7vy6nl10fg.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Nanako Shiraishi <nanako3@lavabit.com> writes:
>
>> Quoting Jeff King <peff@peff.net>
>>
>>> Subject: [PATCH] pull: improve advice for unconfigured error case
>>> ...
>> Junio, may I ask what happened to this patch?
>
> Thanks for prodding. Unfortunately I lost track. Will look at it again
> but probably not tonight.
Applied the patch as-is, as it looked quite good.
Thanks.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox