Push and pull are not opposite operations: the opposite of push is fetch. This is because pull updates the working copy, while push does After running this: $ cat A A $ cat ../r1/A AA The working copy in r2 was not updated with the changes you pushed to it (both the content and the mode change). --

We're getting ready for the git 1.6 release in the not-too-distant future, and that will ship with gitgui-0.11. The current tip of my master branch builds as follows. There have not been many changes in the interface so I don't think there is much (if any) translation work for this release. MSGFMT po/de.msg 402 translated. MSGFMT po/fr.msg 391 translated. MSGFMT po/hu.msg 391 translated. MSGFMT po/it.msg 390 translated, 1 untranslated. MSGFMT po/ja.msg 391 tr...

Oh. Its updated now, but msgmerge on my system is busted and won't update the po files themselves. *sigh* -- Shawn. --

Thanks. There have been a handful gitweb patches on the list recently (I think they were all post -rc0 feature enhancements, but I may be mistaken). I'm wondering what their status are. Does any of them matter in the current cycle? By the way, I've privately pinged Paul for gitk status. --

Just a quick question before the weekend ends and -rc2 gets tagged. (I lost track of that argv0 vs bin/git vs libexec/git-core/git-foo discussion). Are there any missing but necessary patches we need before 1.6.0 for MinGW? --

Ok on idea, but NAK on implementation. "A\?" to mean 0 or one "A" in BRE is GNU extention and we try to avoid it. "A\{0,1\}" is equivalent and we already use the bound notation in "java" section, so perhaps this is an Ok replacement? { "tex", "^\\(\\\\\\(\\(sub\\)*section\\|chapter\\|part\\)\\*\\{0,1\\}{.*\\)$" }, --

At the moment it seems to me that the post-receive hook is not called when tracking a remove Subversion repository. I think it would be nice to call the post-receive hook at the end of: $ git svn rebase Why I need this? I'd like to check for example that if a file has been added to the remote Subversion repository then it is properly added into a MANIFEST file. I'd also like to check some style rules. This would help to detect some problems when one has no way to add hooks on the S...

Hum... Any hook is very specific to a project. That's why it is a hook and not a built-in command. BTW, I do not see why this would be a problem with git-svn whereas the post-receive hook is fine for Git. In many projects rewriting history is not permitted but post-receive is quite handy to do some checks. post-received receive 3 parameters: - sha before - sha after - refname It is perfectly usable after a git-svn rebase. Pascal. -- --|-------------------------...

That would be nice, but as far as I understand that is not possible without ugly hacks like subversion's mod_svn or a CGI script. Or did you refer to the later?

This patch turns ref markers for tags and heads into links to shortlog/refname. Appropriate changes are made in the CSS to prevent ref markers to be annoyingly blue and underlined. Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com> --- gitweb/gitweb.css | 5 +++++ gitweb/gitweb.perl | 5 ++++- 2 files changed, 9 insertions(+), 1 deletions(-) diff --git a/gitweb/gitweb.css b/gitweb/gitweb.css index aa0eeca..2b43eea 100644 --- a/gitweb/gitweb.css +++ b/gitweb/gitweb.css ...

Some projects write ChangeLog entries and use those for svn commit messages. Converting such a repository makes for a most uninteresting git log --pretty=oneline output. 482cfc6... 2008-08-01 Kohei Yoshida <kyoshida@novell.com> 90c16d7... 2008-08-01 Fong Lin <pflin@novell.com> * patches/dev300/cws-npow 505fc23... 2008-08-01 Kohei Yoshida <kyoshida@novell.com> 4729379... 2008-08-01 Kohei Yoshida <kyoshida@novell.com> 9e34b85... 2008-07-31 Kohei ...

Oops :-) I have EMAIL='Jan Nieuwenhuizen <janneke@gnu.org>' so I should probably use GIT_EMAIL='janneke@gnu.org' or something. I'll have a look. Jan. -- Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org --

If you're not sure, please make up your mind. I agree it's quite a hack but now it's in the archives for others to find. Doing this in a single regexp is a bit tricky and asking a user to write a perl snippet is even worse, imho. Especially if would turn out that stripping changelog bits is the only thing that the hook is getting used for, in the end. I have gotten more careful to provide generic solutions to specific problems in anticipation of possible future desires. I could imagine that l...

The subject says it all. Thanks for the new features. Christian

[Empty message]

This patch enhances the tex funcname by adding support for chapter and part sectioning commands. It also matches the starred version of the sectioning commands. Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com> --- Resend, with Signed-off-by: line diff.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/diff.c b/diff.c index c253015..776bce1 100644 --- a/diff.c +++ b/diff.c @@ -1380,7 +1380,7 @@ static struct builtin_funcname_pattern { "^[ ...

-- Shawn. --

Signed-off-by: Stephan Beyer <s-beyer@gmx.net> --- builtin-revert.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/builtin-revert.c b/builtin-revert.c index e9da870..27881e9 100644 --- a/builtin-revert.c +++ b/builtin-revert.c @@ -180,7 +180,7 @@ static void set_author_ident_env(const char *message) email++; timestamp = strchr(email, '>'); if (!timestamp) - die ("Could not extract author email from %s", + die ("Could not extract author tim...

-- Shawn. --

Hmm. The has_doubledash test seems redundant since we don't do anything with args that aren't --foo. Even though git-grep will accept a tree-ish and thus completion of __git_refs here may make sense. I wonder if we shouldn't just add to the end something like: __gitcomp "$(__git_refs)" like the _git_reset function does. Then we can complete a tree-ish for searching, as well as honor -- to stop tree-ish completion and go back to file/directory completion. But that is very much a user...

Yes it does. The CONNECT method is used to get a full-duplex channel to a remote site through a HTTP proxy. The downside with that is of course that most proxies are setup to disallow CONNECT to other ports than 443 (the https default port). -- / daniel.haxx.se --

On what projects? I'm currently using Git over HTTP (read-only) a lot and it doesn't seem really all that impractical to me. Maybe just using a more dumb-friendly packing scheme could help a lot? Petr "Pasky" Baudis --

I think this is going in the right direction, but I have to wonder a few things. First, on hash-object. (1) "hash-object --stdin" always hashes literally. We may want to be able to say "The contents is this but pretend it came from this path and apply the usual input rules", perhaps with "--path=" option; (2) "hash-object temporaryfile" may want to honor the same "--path" option; (3) "hash-object --stdin-paths" may want to get pair of paths (i.e. two lines per entr...

The command line $ git clone --mirror $URL is now a short-hand for $ git clone --bare $URL $ (cd $(basename $URL) && git remote add --mirror origin $URL) Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> --- Interdiff to follow. Documentation/git-clone.txt | 5 ++++- builtin-clone.c | 24 ++++++++++++++++++++---- t/t5601-clone.sh | 10 ++++++++++ 3 files changed, 34 insertions(+), 5 deletions(-) diff --git a/Documenta...

The interdiff: diff --git a/builtin-clone.c b/builtin-clone.c index a45179c..ecdcefa 100644 --- a/builtin-clone.c +++ b/builtin-clone.c @@ -347,6 +347,7 @@ int cmd_clone(int argc, const char **argv, const char *prefix) char branch_top[256], key[256], value[256]; struct strbuf reflog_msg; struct transport *transport = NULL; + char *src_ref_prefix = "refs/heads/"; struct refspec refspec; @@ -445,7 +446,9 @@ int cmd_clone(int argc, const char **argv, const char *prefix) git_config...