On Wed, Sep 19, 2012 at 10:31:58AM -0700, Junio C Hamano wrote:
> Torsten Louland writes:
>
> > Installing latest stable git on Mac OS X Mountain Lion is blocked
> > by Gatekeeper.
> >
> > Could you provide an installer for latest stable git that is
> > signed with an Apple issued developer ID s
On Sat, Sep 22, 2012 at 09:37:38AM +1000, Paul J R wrote:
> Im not sure if this is a bug, or just "as implemented". But when
> cloning from a repo sitting on a web site that uses basic auth, the
> git client appears to forget its authentication info and ignores the
> 401's the server is sending ba
Here's a patch.
-- 8< --
From: Ramkumar Ramachandra
Date: Sat, 22 Sep 2012 10:25:10 +0530
Subject: [PATCH] test-lib: do not trust $SHELL
Do not trust $SHELL to be a bourne-compatible shell. Instead, use the
Makefile variable $SHELL_PATH. This fixes a bug: when a test was run
with --tee and $SH
Hi again,
On Sat, Sep 22, 2012 at 10:22 AM, Junio C Hamano wrote:
> Ramkumar Ramachandra writes:
>
>> Junio C Hamano wrote:
>>> The reference to ${SHELL-/bin/sh} in the test need to be updated to
>>> SHELL_PATH as Peff suggested in the other subthread.
>>
>> For that, the entire block needs to b
Ramkumar Ramachandra writes:
> Junio C Hamano wrote:
>> The reference to ${SHELL-/bin/sh} in the test need to be updated to
>> SHELL_PATH as Peff suggested in the other subthread.
>
> For that, the entire block needs to be moved down to come after `.
> GIT_BUILD_DIR="$TEST_DIRECTORY"/..`. Is thi
Joshua Jensen writes:
> Background: To tie Perforce changelists to Git commits, I add a note
> to a commit with the form "P4@123456". Later, I use the note to sync
> down the closest Perforce changelist matching the Git commit.
I noticed that nobody brought this up, but probably it should not b
TODO: should only be enabled explicitly to avoid unexpected trimming
Signed-off-by: Nguyễn Thái Ngọc Duy
---
And I did not remember I was in interactive rebase mode when I made
the series. This patch is for discussion only. My screen seems to
flash (I think) printing trailing spaces.
pretty.
Hi Junio,
Junio C Hamano wrote:
> The reference to ${SHELL-/bin/sh} in the test need to be updated to
> SHELL_PATH as Peff suggested in the other subthread.
For that, the entire block needs to be moved down to come after `.
GIT_BUILD_DIR="$TEST_DIRECTORY"/..`. Is this okay?
diff --git a/t/test-
This also adds color support to format_decoration()
Signed-off-by: Nguyễn Thái Ngọc Duy
---
log-tree.c | 59
log-tree.h | 3 ++
pretty.c | 19 +
t/t4207-log-decoration-colors
Either %<, %> or %<> standing before a placeholder specifies how many
columns (at least as the placeholder can exceed it) it takes. Each
differs on how spaces are padded:
%< pads on the right (aka left alignment)
%> pads on the left (aka right alignment)
%<> pads both ways equally (aka cente
Signed-off-by: Nguyễn Thái Ngọc Duy
---
utf8.c | 20 ++--
utf8.h | 1 +
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/utf8.c b/utf8.c
index 18a4d9c..791499e 100644
--- a/utf8.c
+++ b/utf8.c
@@ -266,18 +266,26 @@ int utf8_width(const char **start, size_t *remain
Signed-off-by: Nguyễn Thái Ngọc Duy
---
utf8.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/utf8.c b/utf8.c
index a544f15..18a4d9c 100644
--- a/utf8.c
+++ b/utf8.c
@@ -9,6 +9,20 @@ struct interval {
int last;
};
+static size_t display_m
Signed-off-by: Nguyễn Thái Ngọc Duy
---
Documentation/pretty-formats.txt | 1 +
pretty.c | 28 +++-
2 files changed, 28 insertions(+), 1 deletion(-)
diff --git a/Documentation/pretty-formats.txt b/Documentation/pretty-formats.txt
index e3d8a83..8
Signed-off-by: Nguyễn Thái Ngọc Duy
---
pretty.c | 60 +++-
1 file changed, 35 insertions(+), 25 deletions(-)
diff --git a/pretty.c b/pretty.c
index e910679..93c96c2 100644
--- a/pretty.c
+++ b/pretty.c
@@ -863,6 +863,40 @@ static int form
Still a toy series (previous discussion [1]) but it's getting close to
something useful.
This introduces three placeholders %<, %> and %<> for
left/right/center align the next placeholder. Any of them can be
followed by '|' to make the next placeholder use up to the Nth column.
It's pretty useful
Jeff King writes:
> I think people have provided sane techniques for doing this with a
> pipeline. But there is really no reason not to have --grep-notes, just
> as we have --grep. It's simply that nobody has implemented it yet (and
> nobody is working on it as far as I know). It would actually
Hi All,
Im not sure if this is a bug, or just "as implemented". But when cloning
from a repo sitting on a web site that uses basic auth, the git client
appears to forget its authentication info and ignores the 401's the
server is sending back. It appears to initially login and get refs and
HE
On Fri, Sep 21, 2012 at 03:10:40PM -0600, Joshua Jensen wrote:
> - Original Message -
> From: Johannes Sixt
> Date: 9/21/2012 2:50 PM
> >The trick is to pipe 'git log' output into another process that reads no
> >more than it needs and exits. Then 'git log' dies from SIGPIPE before it
> >p
Andreas Schwab writes:
> Ramkumar Ramachandra writes:
>
>> My SHELL_PATH is not set, and I can see SHELL_PATH ?= $(SHELL) in the
>> Makefile. Which shell is it supposed to point to?
>
> Inside a makefile the variable SHELL is special in that it is never
> imported from the environment. If not
On Sat, Sep 22, 2012 at 03:04:50AM +0530, Ramkumar Ramachandra wrote:
> > No, the #!-header is only information. When you run "make test" we
> > actually invoke the shell ourselves using $SHELL_PATH.
>
> My SHELL_PATH is not set, and I can see SHELL_PATH ?= $(SHELL) in the
> Makefile. Which shel
Ramkumar Ramachandra writes:
> Hi Peff,
>
> Jeff King wrote:
>> On Sat, Sep 22, 2012 at 02:37:38AM +0530, Ramkumar Ramachandra wrote:
>>
>>> > I don't think that is the right thing to do. The point of SHELL is to
>>> > point at a bourne-compatible shell. On some systems, the main reason to
>>> >
Ramkumar Ramachandra writes:
> My SHELL_PATH is not set, and I can see SHELL_PATH ?= $(SHELL) in the
> Makefile. Which shell is it supposed to point to?
Inside a makefile the variable SHELL is special in that it is never
imported from the environment. If not set it defaults to /bin/sh.
Andrea
From: Ryan Cumming
git p4 was moved out of contrib in 1.7.11 but it git-completion didn't
know about it. Add git p4 completion based on the existing SVN
completion. It covers all known subcommands and options except for the
-/ option for clone which doesn't use the standard -- prefix.
Signed-off
Hi Peff,
Jeff King wrote:
> On Sat, Sep 22, 2012 at 02:37:38AM +0530, Ramkumar Ramachandra wrote:
>
>> > I don't think that is the right thing to do. The point of SHELL is to
>> > point at a bourne-compatible shell. On some systems, the main reason to
>> > set it is that /bin/sh is _broken_, and w
On Fri, Sep 21, 2012 at 11:08:34PM +0200, Andreas Schwab wrote:
> Jeff King writes:
>
> > A bigger question is: why are you setting SHELL=zsh in the first place?
>
> SHELL is set to the login shell by default.
Yeah, sorry, I was thinking this was coming from our $SHELL_PATH
Makefile variable,
On Sat, Sep 22, 2012 at 02:37:38AM +0530, Ramkumar Ramachandra wrote:
> > I don't think that is the right thing to do. The point of SHELL is to
> > point at a bourne-compatible shell. On some systems, the main reason to
> > set it is that /bin/sh is _broken_, and we are trying to avoid it.
>
> Bu
- Original Message -
From: Johannes Sixt
Date: 9/21/2012 2:50 PM
The trick is to pipe 'git log' output into another process that reads no
more than it needs and exits. Then 'git log' dies from SIGPIPE before it
processed all 1000 commits because its down-stream has gone away.
For example
Jeff King writes:
> A bigger question is: why are you setting SHELL=zsh in the first place?
SHELL is set to the login shell by default.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely
Hi,
Jeff King wrote:
> On Sat, Sep 22, 2012 at 02:22:46AM +0530, Ramkumar Ramachandra wrote:
>
>> Replace $SHELL with an explicit `/bin/sh`, as some shells do not
>> support all the features used in the script. For example, ZSH does
>> not respect IFS, which is used in line 478.
>
> I don't think
Junio C Hamano writes:
> Let's do this for now instead. That would make it clear to people
> who (rightly or wrongly) think the "--follow" option should do
> something that we already do so, and explain the output that they
> see when they do give the "--follow" option to the command.
>
> I may
On Sat, Sep 22, 2012 at 02:22:46AM +0530, Ramkumar Ramachandra wrote:
> Replace $SHELL with an explicit `/bin/sh`, as some shells do not
> support all the features used in the script. For example, ZSH does
> not respect IFS, which is used in line 478.
I don't think that is the right thing to do.
Replace $SHELL with an explicit `/bin/sh`, as some shells do not
support all the features used in the script. For example, ZSH does
not respect IFS, which is used in line 478.
Signed-off-by: Ramkumar Ramachandra
---
t/test-lib.sh |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
Am 21.09.2012 22:25, schrieb Joshua Jensen:
> - Original Message -
> From: Junio C Hamano
> Date: 9/21/2012 2:04 PM
>> Joshua Jensen writes:
>>
Is there any particular reason you do that as two separate steps?
It would feel more natural, at least to me, to do something along
On Fri, Sep 21, 2012 at 10:13:09PM +0200, Stefano Lattarini wrote:
> On 09/21/2012 09:58 PM, Ramkumar Ramachandra wrote:
> > Hi again,
> >
> > Ramkumar Ramachandra wrote:
> >> I was able to reproduce the problem on all my machines, and I consider
> >> this very disturbing. However, I was success
Hi again,
Ramkumar Ramachandra wrote:
> ... but didn't we set $IFS for this purpose? The following segment of
> code works:
I'm sorry, it doesn't. That is the problem.
Ram
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
Mo
- Original Message -
From: Junio C Hamano
Date: 9/21/2012 2:04 PM
Joshua Jensen writes:
Is there any particular reason you do that as two separate steps?
It would feel more natural, at least to me, to do something along
the lines of
git log --show-notes=p4notes -1000
Thanks
Hi Stefano,
Stefano Lattarini wrote:
> Zsh doesn't do word-splitting by default on variable expansions:
>
> $ zsh -c 'v="1 2 3"; for x in $v; do echo "$x"; done'
> 1 2 3
>
> unless you set the SH_WORD_SPLIT option, or put Zsh in Bourne-compatibility
> mode somehow:
... but didn't we set $
On 09/21/2012 09:58 PM, Ramkumar Ramachandra wrote:
> Hi again,
>
> Ramkumar Ramachandra wrote:
>> I was able to reproduce the problem on all my machines, and I consider
>> this very disturbing. However, I was successfully able to corner the
>> issue. I have an overtly long $PATH that's not getti
Joshua Jensen writes:
>> Is there any particular reason you do that as two separate steps?
>> It would feel more natural, at least to me, to do something along
>> the lines of
>>
>> git log --show-notes=p4notes -1000
>>
>>
> Thanks for the reply.
>
> I did not make clear above that I want to
Adam Spiers writes:
> +expect_in () {
> + dest="$HOME/expected-$1" text="$2"
> + if test -z "$text"
> + then
> + >"$dest" # avoid newline
> + else
> + echo -e "$text" >"$dest"
This breaks when your shell is not "bash".
> +test_check_ignore () {
> + ar
Hi Peff,
I was able to reproduce the problem on all my machines, and I consider
this very disturbing. However, I was successfully able to corner the
issue. I have an overtly long $PATH that's not getting split properly
by `IFS=:` in one corner case -- in other words, this shell script
fails to ex
Jeff King writes:
> On Wed, Sep 19, 2012 at 01:31:50PM -0700, Kevin Ballard wrote:
>
>> > I am a little lukewarm on my patch if only because of the precedent it
>> > sets. There are a trillion options that revision.c parses that are not
>> > necessarily meaningful or implemented for sub-commands
Hi.
We've been running with core.autocrlf = input (some people with
core.autocrlf = true). However, there are some text files in the
repository that are CRLF, and I am at a loss to explain how they go here.
We understand that if core.autocrlf=false, this could happen. While I
admit there i
Adam Spiers writes:
> It has been rebased on the latest master, and passed a full test run.
FYI, I applied the attached on top before queuing it in 'pu'.
Points to note:
* We match the underline and the title of documentation header;
* a few type mismatches (constness of full_path and treat
That doesn't solve the mystery why you need libiconv in the first place.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsub
- Original Message -
From: Andreas Schwab
Date: 9/21/2012 9:10 AM
Joshua Jensen writes:
Background: To tie Perforce changelists to Git commits, I add a note to a
commit with the form "P4@123456". Later, I use the note to sync down the
closest Perforce changelist matching the Git commi
- Original Message -
From: Junio C Hamano
Date: 9/21/2012 11:21 AM
Joshua Jensen writes:
Background: To tie Perforce changelists to Git commits, I add a note
to a commit with the form "P4@123456". Later, I use the note to sync
down the closest Perforce changelist matching the Git comm
Lovely... I found the solution. So want to share with you all.
Solution : add /usr/local/lib to /etc/ld.so.conf and run sudo ldconfig
ld.so.conf file includes ld.so.conf.d/*.conf
so I created local-lib.conf having value /usr/local/lib and place
local-lib.conf under /etc/ld.so.conf.d directo
Nguyen Thai Ngoc Duy writes:
>> - How does this interact with the wrapped output? Should it?
>
> We have to deal with it anyway when the left aligned text takes all
> the space. On one hand, I don't want to break the terminal width,
> leading to ugly output, so it'll interact. On the other hand
On Fri, Sep 21, 2012 at 10:34:22AM -0700, Junio C Hamano wrote:
> >> > I'm half-tempted to just drop the config entirely, leave
> >> > GIT_SMART_HTTP=false as an escape hatch, and see if anybody even cares.
> >>
> >> Sounds like a very attractive minimalistic way to go forward. We
> >> can alway
On Fri, Sep 21, 2012 at 10:25:24AM -0700, Junio C Hamano wrote:
> > However, this does make things more consistent with upload-pack, which
> > connects the stderr of pack-objects to sideband (which it must to handle
> > progress). Furthermore, many of the messages from receive-pack are
> > handled
Jeff King writes:
> On Thu, Sep 20, 2012 at 02:15:20PM -0700, Junio C Hamano wrote:
>
>> Jeff King writes:
>>
>> > I'm half-tempted to just drop the config entirely, leave
>> > GIT_SMART_HTTP=false as an escape hatch, and see if anybody even cares.
>>
>> Sounds like a very attractive minimalis
I have tried with iconv by adding its path in PATH and LIBRARY Path but failed
to get any solution...
Still getting below error
c:\Ankush Data\work\Test-GIT\trial_1>git clone
ssh://bea@:/home/bea/GIT/sample_project
Cloning into 'sample_project'...
bea@.:'s password:
git-upload-pack: error while
Jeff King writes:
> On Fri, Sep 21, 2012 at 09:49:40AM -0700, Junio C Hamano wrote:
>
>> > 2. No matter what the cause, we are probably better off
>> > showing the errors to the client. If the client and the
>> > server admin are not the same entity, it is probably
>> > much easi
Joshua Jensen writes:
> Background: To tie Perforce changelists to Git commits, I add a note
> to a commit with the form "P4@123456". Later, I use the note to sync
> down the closest Perforce changelist matching the Git commit.
>
> I search for these notes by getting a list of revisions:
>
>
Chris Hiestand writes:
> My email in April went unanswered so I'm resending it. An Auto-Submitted
> header
> would be an improvement to the standard [git] post receive email.
>
> Thanks,
> Chris
>
>
> Begin forwarded message:
>
>> From: Chris Hiestand
>> Subject: [PATCH] Add Auto-Submitted head
On Tue, Sep 18, 2012 at 12:51 AM, Junio C Hamano wrote:
> Martin von Zweigbergk writes:
>
>> do you agree
>> that 'rebase --onto does not re-apply patches in onto' is desirable?
>
> This depends on how you look at --onto. Recall the most typical and
> the original use case of rebase:
>
>
On Fri, Sep 21, 2012 at 09:49:40AM -0700, Junio C Hamano wrote:
> > 2. No matter what the cause, we are probably better off
> > showing the errors to the client. If the client and the
> > server admin are not the same entity, it is probably
> > much easier for the client to cut-an
Agreed, that would be very nice.
For the EU location, I would personally sponsor London, possibly at some
well-know location such as "Skills Matters"
Luca.
On 21 Sep 2012, at 17:55, Patrick Renaud wrote:
> THAT would be awesome :-)
>
> On 21 September 2012 12:45, Scott Chacon wrote:
>> Actua
THAT would be awesome :-)
On 21 September 2012 12:45, Scott Chacon wrote:
> Actually, responding to some of the feedback I've been getting, I'm
> thinking of having a single day of just core developers and then a day
> or two of users, or vice versa, but doing them together in a single
> event.
Jeff King writes:
> Receive-pack invokes either unpack-objects or index-pack to
> handle the incoming pack. However, we do not redirect the
> stderr of the sub-processes at all, so it is never seen by
> the client. From the initial thread adding sideband support,
> which is here:
>
> http://thr
Actually, responding to some of the feedback I've been getting, I'm
thinking of having a single day of just core developers and then a day
or two of users, or vice versa, but doing them together in a single
event. Then just doing that same pattern in both the EU and the US.
Scott
On Fri, Sep 21,
Guys,
Are we still talking of having two disconnected events for Git, one
for core devs and one for users?
-Patrick
On 21 September 2012 11:23, Christian Couder wrote:
> On Fri, Sep 21, 2012 at 4:05 PM, Shawn Pearce wrote:
>> On Fri, Sep 21, 2012 at 2:20 AM, Christian Couder
>>
>>> It is sad t
Michael Haggerty writes:
>> +For each pathname given via the command-line or from a file via
>> +`--stdin`, this command will list the first exclude pattern found (if
>> +any) which explicitly excludes or includes that pathname. Note that
>> +within any given exclude file, later patterns take pr
Michael Haggerty writes:
> On 09/20/2012 09:46 PM, Adam Spiers wrote:
>> Signed-off-by: Adam Spiers
>> ---
>> Documentation/technical/api-directory-listing.txt | 2 ++
>> dir.c | 23
>> +--
>> dir.h
On Fri, Sep 21, 2012 at 4:05 PM, Shawn Pearce wrote:
> On Fri, Sep 21, 2012 at 2:20 AM, Christian Couder
>
>> It is sad that people who know what is or what is not happening are
>> not taking care of letting people on this list know about it...
>
> I did not post to this mailing list about the Ger
Joshua Jensen writes:
> Background: To tie Perforce changelists to Git commits, I add a note to a
> commit with the form "P4@123456". Later, I use the note to sync down the
> closest Perforce changelist matching the Git commit.
>
> I search for these notes by getting a list of revisions:
>
>
Background: To tie Perforce changelists to Git commits, I add a note to
a commit with the form "P4@123456". Later, I use the note to sync down
the closest Perforce changelist matching the Git commit.
I search for these notes by getting a list of revisions:
git rev-list --max-count=100
On Fri, Sep 21, 2012 at 4:19 PM, Scott Chacon wrote:
>>> I'm also very much interested in attending a gathering Berlin, though
>>> preferably not in the first week of October. As I'm a local, I could
>>> probably also help with finding a location if necessary.
>
> If you would like, I would love
On Thu, Sep 20, 2012 at 10:26 PM, Jeff King wrote:
> On Thu, Sep 20, 2012 at 04:05:03PM -0700, Shawn O. Pearce wrote:
>
>> But right now I am seeing failures in libcurl's SSL connection that
>> may also be causing the smart connection failures. For example this
>> trace, where libcurl was just not
On Fri, Sep 21, 2012 at 07:05:53AM -0700, Shawn O. Pearce wrote:
> I have no further information about the potential GitTogether than
> anyone else. IIRC there is a suggestion in this thread about hosting
> something in the EU sometime in early next year, with someone at
> GitHub acting as organiz
On Fri, Sep 21, 2012 at 2:20 AM, Christian Couder
wrote:
> On Thu, Sep 20, 2012 at 8:53 PM, Sebastian Schuberth
> wrote:
>> On 19.09.2012 15:43, Michael Haggerty wrote:
>>
>>> Is there any news about the proposed gatherings? I would be quite
>>> interested in attending the developer meeting. Oc
On Thu, Sep 20, 2012 at 09:40:49AM -0700, Junio C Hamano wrote:
> - I am wondering if somebody ever want to do this with a follow-up
>patch:
>
> Left %h%|Center %cd%|Right %ad
>
>Is %| a sensible choice for "flush right"? I am wondering if it
>makes more sense to make %|, %< a
Hi,
On Thu, Sep 20, 2012 at 8:53 PM, Sebastian Schuberth
wrote:
> On 19.09.2012 15:43, Michael Haggerty wrote:
>
>> Is there any news about the proposed gatherings? I would be quite
>> interested in attending the developer meeting. October is just around
>> the corner...what's up?
>
>
> I'm als
My email in April went unanswered so I'm resending it. An Auto-Submitted header
would be an improvement to the standard [git] post receive email.
Thanks,
Chris
Begin forwarded message:
> From: Chris Hiestand
> Subject: [PATCH] Add Auto-Submitted header to post-receive-email
> Date: April 14, 2
On Thu, Sep 20, 2012 at 11:40 PM, Junio C Hamano wrote:
> I think this is a great feature at the conceptual level, and you
> know "but" is coming ;-).
I'm still not sure if it's useful beyond my simple example. For
example, will it be useful in multiline log format, not just
--oneline?
> - Shou
On Fri, Sep 21, 2012 at 12:47 AM, Junio C Hamano wrote:
>>> +- '%C+': enable coloring on the following placeholders if supported
>>> +- '%C-': disable coloring on the following placeholders
>>
>> OK, so typically you replace some format placeholder "%?" in your
>> format string with "%C+%?%C-", be
On 09/20/2012 09:46 PM, Adam Spiers wrote:
> Signed-off-by: Adam Spiers
> ---
> Documentation/technical/api-directory-listing.txt | 2 ++
> dir.c | 23
> +--
> dir.h | 1 +
> 3 files cha
On 09/20/2012 09:46 PM, Adam Spiers wrote:
> This is in preparation for reuse by a new git check-ignore command.
>
> Signed-off-by: Adam Spiers
> ---
> Makefile | 2 ++
> builtin/add.c | 95 ++---
> pathspec.c| 97
> +
On 09/20/2012 09:46 PM, Adam Spiers wrote:
> This works in a similar manner to git-check-attr. Some code
> was reused from add.c by refactoring out into pathspec.c.
>
> Thanks to Jeff King and Junio C Hamano for the idea:
> http://thread.gmane.org/gmane.comp.version-control.git/108671/focus=10881
80 matches
Mail list logo
