We need to use git-upload-pack, not git-receive-pack. This was broken by accident in 57aa472a7ef5e9349c4c0aa1a3022a1e28499324. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> --- .../org/spearce/jgit/transport/TransportLocal.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/org.spearce.jgit/src/org/spearce/jgit/transport/TransportLocal.java b/org.spearce.jgit/src/org/spearce/jgit/transport/TransportLocal.java index b41d4af..155d59f 100644 --- a/org.spearc...

This command allows us to create simple or annotated tags. PGP signed tags are not yet supported. Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com> --- org.spearce.jgit/src/org/spearce/jgit/pgm/Tag.java | 102 ++++++++++++++++++++ 1 files changed, 102 insertions(+), 0 deletions(-) create mode 100644 org.spearce.jgit/src/org/spearce/jgit/pgm/Tag.java An obvious omission was not to allow the user to tag anything but HEAD. diff --git a/org.spearce.jgit/src/org/spearce/jgit/pg...

I'm a newb to git. I'm trying to "git svn clone" a tried and true subversion repo but it fails after scanning the 2069 commit, and spits out: vendor/plugins/locking/.git/refs/heads/master was not found in commit 484775a7dc66b9c91188a5ad52c30c371ff8d702 (r2068) Which is right. It isn't in 2068, it was checked in at 2069. The 2069 commit was some code I had "git clone"d from github into a subfolder of the parent project that's checked into subversion. I've tried to replicate this behavior...

This option realizes a stupid hack that tries to run the test cases line by line (separated by &&). Furthermore it shows the line it is testing. With that information it is easier to find the reason why a test fails. This hack works as long as there are no multi-line for/while/subshell/... in the test cases. Note, that the -s option should only be used if a test case failed. It is slow and error-prone. Signed-off-by: Stephan Beyer <s-beyer@gmx.net> --- Hi, I wrote that befo...

Oh, there is no misunderstanding. You couldn't have possibly known if the main body of the patch will go to 'next' or just be dropped when I said The title is probably not 'stash apply' but 'stash branch'. Don't you want to also validate that: - "stash branch" command switched to the new branch "stashbranch"? - before making "alternate second", the index and the working tree have expected contents? and - the final shape of the history looks correctly forked (i.e. "stashbranch" ...

With subversion 1.5.0 (C and perl libraries) the git-svn selftest t9101-git-svn-props.sh fails at test 25 and 26. The following commands cause assertions in the svn library $ cd deeply $ git-svn propget svn:ignore . perl: /build/buildd/subversion-1.5.0dfsg1/subversion/libsvn_ra/ra_loader.c:674: svn_ra_get_dir: Assertion `*path != '/'' failed. Aborted $ git-svn propget svn:ignore .. perl: /build/buildd/subversion-1.5.0dfsg1/subversion/libsvn_subr/path.c:120: svn_path_join: Assertion `is_ca...

Boundary lines in emails are treated as a special case. As a result of processing the boundary line a new line will be read into the buffer. The string length variable 'len' is evaluated before the boundary case, thus there is the possibility the length of the string does not match the new line read in (in the boundary line case). This causes a partial output of the line to the patch file. The fix is trivial, evaluate the length of the string right before processing it. Signed-off-by: Don Zi...

Ack. This patch does indeed seem to fix the test-case I had. Thanks, Linus --

Hi, I'd grep in the output of "git rev-list --objects". Then I'd have the full name, and "git log --all -- <fullpath>" is my friend. Ciao, Dscho --

Hi, If we want to call this "--directory=<root>" instead, we should do it before that commit hits master. Ciao, Dscho --

The stat string was only initialized if the ref was local, but was always used in a printf. This meant that whatever data was on the stack got printed. In the case of "branch -av", this was probably the tracking information of the last local branch. If the case of "branch -rv", this was "@???" in my case. Signed-off-by: Brian Gernhardt <benji@silverinsanity.com> --- After looking through the second get of changes I pulled, I tried this: $ git branch -av * master 31...

Looks good, and more importantly works. Cherry-picked it from pu onto next. Hopefully it'll move there on it's own soon. ~~ Brian --

This makes rebase act a little more like merge when working on the current branch. This is particularly useful for `git pull --rebase` Signed-off-by: Brian Gernhardt <benji@silverinsanity.com> --- Okay, I apparently should stop coding after midnight, even if I think I'm awake enough. This version uses the correct variable. $orig_head looks like the right name, but it stores the symbolic ref. $prev_head stores the actual SHA1, which is what I was looking for. git-rebase.sh | 1...

On Sun, Jul 06, 2008 at 04:00:23AM -0400, Brian Gernhardt <benabik@silverin= My fault, I noticed it but I forgot to send a reminder about it before it hit next. Sorry. (I suppose it won't be fixed, unless merge-in-c won't hit master before 1.6.0, which is hopefully unlikely. ;-) )

Three git versions? --

This unfortunately includes also SRPMS (.src.rpm), even though the source RPM from git repository is not distribution specific. I think that src.rpm should drop '.fc9.' from name -- Jakub Narebski Poland ShadeHawk on #git --

The old text stated that 'git-frotz' can be always used instead of 'git frotz' which is no longer true. Signed-off-by: Miklos Vajna <vmiklos@frugalware.org> --- INSTALL | 18 ++++++------------ 1 files changed, 6 insertions(+), 12 deletions(-) diff --git a/INSTALL b/INSTALL index 4a4e13f..0efb4b7 100644 --- a/INSTALL +++ b/INSTALL @@ -27,20 +27,14 @@ Issues of note: - git normally installs a helper script wrapper called "git", which conflicts with a similarly named "GNU intera...

The function "config_error_nonbool", that is defined in "config.c", is used to report an error when a config key in the config file should have a corresponding value but it hasn't. So the parameter to this function should be the key and not the value, because the value is undefined. And it could crash if the value is used. This patches fixes two occurences where the value was passed instead of the key. Signed-off-by: Christian Couder <chriscool@tuxfamily.org> --- builtin-tag.c | 2 ...

This fixes the following warning: hg-to-git.py:92: DeprecationWarning: raising a string exception is deprecated Signed-off-by: Miklos Vajna <vmiklos@frugalware.org> --- contrib/hg-to-git/hg-to-git.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/contrib/hg-to-git/hg-to-git.py b/contrib/hg-to-git/hg-to-git.py index f68ef72..25d9941 100755 --- a/contrib/hg-to-git/hg-to-git.py +++ b/contrib/hg-to-git/hg-to-git.py @@ -89,7 +89,7 @@ try: if o in ('-v', '-...

This is not just nice but necessary since git-frotz is no longer in PATH. Signed-off-by: Miklos Vajna <vmiklos@frugalware.org> --- contrib/hg-to-git/hg-to-git.py | 20 ++++++++++---------- 1 files changed, 10 insertions(+), 10 deletions(-) diff --git a/contrib/hg-to-git/hg-to-git.py b/contrib/hg-to-git/hg-to-git.py index 130b1c4..61540ef 100755 --- a/contrib/hg-to-git/hg-to-git.py +++ b/contrib/hg-to-git/hg-to-git.py @@ -152,7 +152,7 @@ for cset in range(1, int(tip) + 1): if not ...

'show' is a high-level command, scripts are better if they use 'rev-parse'. Signed-off-by: Miklos Vajna <vmiklos@frugalware.org> --- contrib/hg-to-git/hg-to-git.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/contrib/hg-to-git/hg-to-git.py b/contrib/hg-to-git/hg-to-git.py index 7b03204..0ecb38b 100755 --- a/contrib/hg-to-git/hg-to-git.py +++ b/contrib/hg-to-git/hg-to-git.py @@ -233,7 +233,7 @@ for cset in range(int(tip) + 1): os.system('git branch -...

Presently, it'll actually try to read stdin twice and that won't work. Also, if you want git-bundle to deal with --stdin --stdin, I'd say that git-rev-list should do the same. I don't really care how this particular error case is handled, but I think git-rev-list and git-bundle should do the same thing for any given input. If you prefer to be liberal in what you accept, then you might like these two patches that allow git-rev-list and git-bundle to deal with --stdin --stdin. By the w...

This patch allows the caller to feed the revision parameters to git-bundle from its standard input. This way, a script do not have to worry about limitation of the length of command line. Documentation/git-bundle.txt says that git-bundle takes arguments acceptable to git-rev-list. Obviously some arguments that git-rev-list handles don't make sense for git-bundle (e.g. --bisect) but --stdin is pretty reasonable. Signed-off-by: Adam Brewster <asb@bu.edu> --- bundle.c | 10 ++++++++-- ...

Ah, I missed that. So it is not just warning squelch but is a bugfix in case unsigned and uint32_t are of different sizes. --

Hi, it seems that an old verison on the remote site was the problem: On debian/etch git seems to be too old. I upgraded git to the testing version and now I can delete remote branches. But I get another error: $ git push origin :testbranch To ssh://myserver.com/my/path/to/repository - [deleted] testbranch error: unlink(.git/refs/remotes/origin/testbranch) failed: No such file or directory error: Failed to delete Any idea? Thanks, Martin --