Re: error: unpack failed: unpack-objects abnormal exit

Thanks a lot for replying! That exactly was the problem. We've configured gitosis to allow access over 'ssh://' (Read / Write) while 'git://' access was limited (Read only). Changing the configuration worked out just fine. -Thanks & Regards, Sitesh On Tue, Nov 5, 2013 at 4:33 AM, Jeff King wrot

Re: [PATCH V4] git clone: is an URL local or ssh

Am 11/4/2013 22:20, schrieb Torsten Bögershausen: > Bug fix for msygit in t5601 : use $PWD insted of $(pwd) Not really. $PWD is /c/foo/bar style, but $(pwd) is c:/foo/bar, which is equally good. > test_expect_success 'clone with excess parameters (2)' ' > > rm -fr dst && > - test_mus

Re: [RFC/PATCH] Add interpret-trailers builtin

From: Johan Herland > On Mon, Nov 4, 2013 at 8:12 PM, Junio C Hamano wrote: >> Johan Herland writes: +{ + char *end = strchr(arg, '='); + if (!end) + end = strchr(arg, ':'); >>> >>> So both '=' (preferred) and ':' are accepted as field/value >>> sepa

[PATCH v2] Rename suffixcmp() to has_suffix() and inverse its result

As suffixcmp() should not be used as an ordering comparison function, and anything-cmp() ought to be usable as an ordering comparison function, suffixcmp() should be renamed to something that doesn't end with "cmp". has_suffix() is a straightforward name for such a function, except that with such

Re: [RFC/PATCH] Add interpret-trailers builtin

On Mon, Nov 4, 2013 at 8:12 PM, Junio C Hamano wrote: > Johan Herland writes: >>> +{ >>> + char *end = strchr(arg, '='); >>> + if (!end) >>> + end = strchr(arg, ':'); >> >> So both '=' (preferred) and ':' are accepted as field/value >> separators. That's ok for the comma

[PATCH v2] wt-status: take the alignment burden off translators

It's not easy for translators to see spaces in these strings have to align, especially when there are no guarantees that these strings are grouped together in .po files. Refactor the code and do the alignment automatically. Noticed-by: Wolfgang Rohdewald Signed-off-by: Nguyễn Thái Ngọc Duy ---

Re: error when git-diff get pipe args

On Tue, Nov 05, 2013 at 08:03:28AM +0800, chunguang qu wrote: > $ cat a > 111 > fdsf > 333 > $ cat b > 111 > 222 > 333 > $ git diff a b # OK > diff --git a/a b/b > index 768560b..641d574 100644 > --- a/a > +++ b/b > @@ -1,3 +1,3 @@ > 111 > -fdsf > +222 > 333 > $ git di

Re: [PATCH] Add the commit.gpgsign option to sign all commits

On Mon, Nov 04, 2013 at 03:43:37PM -0800, Junio C Hamano wrote: > Nicolas Vigier writes: > > > If you want to GPG sign all your commits, you have to add the -S option > > all the time. The commit.gpgsign config option allows to sign all > > commits automatically. > > I'm somewhat horrified to im

error when git-diff get pipe args

$ cat a 111 fdsf 333 $ cat b 111 222 333 $ git diff a b # OK diff --git a/a b/b index 768560b..641d574 100644 --- a/a +++ b/b @@ -1,3 +1,3 @@ 111 -fdsf +222 333 $ git diff <(cat a) <(cat b) # ERROR: no result print out diff --git a/dev/fd/63 b/dev/fd/62 index

Re: [PATCH] Add the commit.gpgsign option to sign all commits

On Mon, 04 Nov 2013, Junio C Hamano wrote: > Nicolas Vigier writes: > > > If you want to GPG sign all your commits, you have to add the -S option > > all the time. The commit.gpgsign config option allows to sign all > > commits automatically. > > I'm somewhat horrified to imagine the end-user e

Re: htonll, ntohll

On 31/10/13 13:24, Torsten Bögershausen wrote: > On 2013-10-30 22.07, Ramsay Jones wrote: [ ... ] >> Yep, this was the first thing I did as well! ;-) (*late* last night) >> >> I haven't had time today to look into fixing up the msvc build >> (or a complete re-write), so I look forward to seeing you

Re: [PATCH] Add the commit.gpgsign option to sign all commits

Nicolas Vigier writes: > If you want to GPG sign all your commits, you have to add the -S option > all the time. The commit.gpgsign config option allows to sign all > commits automatically. I'm somewhat horrified to imagine the end-user experience this "feature" adds to the system; if one sets h

[PATCH] Add the commit.gpgsign option to sign all commits

If you want to GPG sign all your commits, you have to add the -S option all the time. The commit.gpgsign config option allows to sign all commits automatically. Signed-off-by: Nicolas Vigier --- Documentation/config.txt | 3 +++ builtin/commit-tree.c| 7 ++- builtin/commit.c | 4

Re: error: unpack failed: unpack-objects abnormal exit

On Fri, Nov 01, 2013 at 04:02:10PM +0530, Sitesh Shrivastava wrote: > I'm using a gitosis server. Suddenly I'm not able to push to the > remote server. Everyone else is able to push to the same server. Btw I > can't push to *any repo* on the server. This is the error I get: > > Counting objects:

Re: [PATCH] builtin/remote: remove postfixcmp() and use suffixcmp() instead

Johannes Schindelin writes: > Hi Junio, > > On Mon, 4 Nov 2013, Junio C Hamano wrote: > >> Junio C Hamano writes: >> >> > I do not think anybody sane uses prefixcmp() or suffixcmp() for >> > anything but checking with zero; in other words, I suspect that all >> > uses of Xcmp() can be replaced

Re: [PATCH] builtin/remote: remove postfixcmp() and use suffixcmp() instead

Hi Junio, On Mon, 4 Nov 2013, Junio C Hamano wrote: > Junio C Hamano writes: > > > I do not think anybody sane uses prefixcmp() or suffixcmp() for > > anything but checking with zero; in other words, I suspect that all > > uses of Xcmp() can be replaced with !!Xcmp(), so as a separate > > clean

Re: [PATCH] Rename suffixcmp() to has_suffix()

On Mon, Nov 04, 2013 at 10:45:11PM +0100, Christian Couder wrote: > diff --git a/builtin/clone.c b/builtin/clone.c > index 874e0fd..4b8308e 100644 > --- a/builtin/clone.c > +++ b/builtin/clone.c > @@ -510,7 +510,7 @@ static void write_followtags(const struct ref *refs, > const char *msg) >

Re: What's cooking in git.git (Nov 2013, #01; Fri, 1)

Thomas Rast writes: > Junio C Hamano writes: > >> * tr/merge-recursive-index-only (2013-10-28) 3 commits >> - merge-recursive: -Xindex-only to leave worktree unchanged >> - merge-recursive: internal flag to avoid touching the worktree >> - merge-recursive: remove dead conditional in update_st

[PATCH] Rename suffixcmp() to has_suffix()

As suffixcmp() should not be used as an ordering comparison function, and anything-cmp() ought to be usable as an ordering comparison function, suffixcmp() should be renamed to something that doesn't end with "cmp". Signed-off-by: Christian Couder --- Hi Junio, This is a patch, following your la

[PATCH V4] git clone: is an URL local or ssh

Commit 8d3d28f5 added test cases for URLs which should be ssh. Add more tests testing all the combinations: -IPv4 or IPv6 -path starting with "/" or with "/~" -with and without the ssh:// scheme Add tests for ssh:// with port number. When a git repository "foo:bar" exist, git clone will call

[PATCH V4] git clone: is an URL local or ssh

Commit 8d3d28f5 added test cases for URLs which should be ssh. Add more tests testing all the combinations: -IPv4 or IPv6 -path starting with "/" or with "/~" -with and without the ssh:// scheme Add tests for ssh:// with port number. When a git repository "foo:bar" exist, git clone will call

[PATCH V4] git clone: is an URL local or ssh

Commit 8d3d28f5 added test cases for URLs which should be ssh. Add more tests testing all the combinations: -IPv4 or IPv6 -path starting with "/" or with "/~" -with and without the ssh:// scheme Add tests for ssh:// with port number. When a git repository "foo:bar" exist, git clone will call

[PATCH 2/2] strbuf: make it clear that suffixcmp() should not be used for sorting

Nobody sane uses suffixcmp() for anything but checking with zero, but it is not very clear from the implementation that it should not be used for any sorting. So let's make it clear that the callers should not expect anything but "does str have sfx as its suffix, yes or no?". Signed-off-by: Chris

[PATCH 1/2] builtin/remote: remove postfixcmp() and use suffixcmp() instead

Commit 8cc5b290 (git merge -X, 25 Nov 2009) introduced suffixcmp() with nearly the same implementation as postfixcmp() that already existed since commit 211c8968 (Make git-remote a builtin, 29 Feb 2008). The only difference between the two implementations is that, when the string is smaller than t

Re: [PATCH] builtin/remote: remove postfixcmp() and use suffixcmp() instead

Junio C Hamano writes: > I do not think anybody sane uses prefixcmp() or suffixcmp() for > anything but checking with zero; in other words, I suspect that all > uses of Xcmp() can be replaced with !!Xcmp(), so as a separate > clean-up patch, we may at least want to make it clear that the > caller

Re: [PATCH] builtin/remote: remove postfixcmp() and use suffixcmp() instead

From: Junio C Hamano Subject: Re: [PATCH] builtin/remote: remove postfixcmp() and use suffixcmp() instead Date: Mon, 04 Nov 2013 11:19:43 -0800 > Christian Couder writes: > >> Commit 8cc5b290 (git merge -X, 25 Nov 2009) introduced >> suffixcmp() with nearly the same implementation as postfixcm

Re: [PATCH] builtin/remote: remove postfixcmp() and use suffixcmp() instead

Christian Couder writes: > Commit 8cc5b290 (git merge -X, 25 Nov 2009) introduced > suffixcmp() with nearly the same implementation as postfixcmp() > that already existed since commit 211c8968 (Make git-remote a > builtin, 29 Feb 2008). This "nearly the same" piqued my curiosity ;-) The postfix

Re: [RFC/PATCH] Add interpret-trailers builtin

Johan Herland writes: Thanks for looking this over. I am mostly in agreement and will elide the parts I do not have much to add. >> This command should help with RFC 822 style headers, called >> "trailers", that are found at the end of commit messages. > > As has been asked earlier in this disc

Re: [RFC/PATCH] Add interpret-trailers builtin

Christian Couder writes: > This RFC patch shows the work in progress to implement a new > command: > > git interpret-trailers > > 1) Rational: > > This command should help with RFC 822 style headers, called > "trailers", that are found at the end of commit messages. > > For a long time, the

Re: [PATCH] wt-status: take the alignment burden off translators

Nguyễn Thái Ngọc Duy writes: > + static const char *spaces = ""; I do not see anything that limits "len" used to show only show the prefix bytes in this array not to ask for more than you have spaces here. It won't overrun the end of this array, but I suspec

Re: [PATCH v3] push: Enhance unspecified push default warning

Greg Jacobson writes: > Is there anything I could do to improve this patch? Thank you. My vague recollection is that we started from an excerpt from the documentation page, not unlike this patch attempts to, but because such an excerpt has to be less complete than the documentation for brevity'

Re: [PATCH 1/3] for-each-ref: introduce %C(...) for color

Ramkumar Ramachandra writes: > Junio C Hamano wrote: >> This patch is about for-each-ref and your series does not seem to >> aim to unify it in any way with pretty-formats, so I would have >> expected an enhancement in line with the former, not the latter. > > While I might never attempt a unific

Re: What's cooking in git.git (Nov 2013, #01; Fri, 1)

Torstein Hegge writes: > On Fri, Nov 01, 2013 at 15:52:06 -0700, Junio C Hamano wrote: >> * th/reflog-annotated-tag (2013-10-28) 1 commit >> (merged to 'next' on 2013-11-01 at 8b154cc) >> + reflog: handle lightweight and annotated tags equally >> >> "git log -g $annotated_tag", when there is

Re: [PATCH] builtin/remote: remove postfixcmp() and use suffixcmp() instead

Christian Couder wrote: > Commit 8cc5b290 (git merge -X, 25 Nov 2009) introduced > suffixcmp() with nearly the same implementation as postfixcmp() > that already existed since commit 211c8968 (Make git-remote a > builtin, 29 Feb 2008). [...] > Signed-off-by: Christian Couder > --- > builtin/remo

Re: What's cooking in git.git (Nov 2013, #01; Fri, 1)

Ramsay Jones writes: > On 01/11/13 22:52, Junio C Hamano wrote: >> Here are the topics that have been cooking. Commits prefixed with >> '-' are only in 'pu' (proposed updates) while commits prefixed with >> '+' are in 'next'. >> > [ ... ] >> >> >> * fc/transport-helper-fixes (2013-11-01) 11 co

Re: [PATCH v2] gitk: Add a horizontal scrollbar for commit history

On 13-10-31 05:05 AM, Paul Mackerras wrote: > On Wed, Oct 30, 2013 at 01:47:08PM +0100, Nicolas Cornu wrote: >> This is useful on all our repos, every times, as we put a tag per day. >> If the HEAD didn't move during 150 days, we got 150 tags. > > Here is a patch that I did some time ago but have

eccellenza del lusso russia emirati arabi

Fashion Vip Magazine ** Speciale Salone del Mobile** -- If you do not want to receive any more newsletters, http://dem.fashionvipmagazine.com/lists/?p=unsubscribe&uid=28f5b000728b6a9507611f37112d001e To update yo