2012/9/3 Junio C Hamano :
> Marco Stornelli writes:
>
>> I tried the Johannes's script, but it seems it doesn't work well with
>> the pattern of format-patch (To: ,\n ,\n
>> ). The multilines are not well managed.
>
> I am guessing that the reason why Jonahhes's "copy our headers out
> with cont
Nguyen Thai Ngoc Duy writes:
>> For this particular scenario, I do not see anything offhand that is
>> unclear about the behaviour of Git in the documentation, even though
>> as you pointed out, if the user is unaware that the shell passes
>> globs unmodified when they do not match, it may lead t
Keep it in the list.
Angelo Borsotti writes:
> Hi Carlos,
>>
>> That grouping is not what it's saying. It doesn't update the files that
>> exist in the working tree matching some glob. It updates the files in
>> the working tree from either the index or a treeish. The pathspec
>> refers, as alw
On Tue, Sep 4, 2012 at 2:36 AM, Junio C Hamano wrote:
>> It's confusing but I don't think there's much we can do about it.
>
> The user can, by telling the shell to expand '*' that does not match
> to nothing, though.
It works 99% the time, I don't think any users would bother setting
that or stu
On Tue, Sep 4, 2012 at 2:26 AM, Junio C Hamano wrote:
> Nguyễn Thái Ngọc Duy writes:
>
>> fetch does printf("%-*s", width, "foo") where "foo" can be an utf-8
>> string, but width is bytes, not letters. This results in misaligned
>> ref summary table.
>
> "but width is bytes, not letters" is a mi
Hi all,
I already posted this question in the git users groups
(https://groups.google.com/forum/?fromgroups=#!topic/git-users/dguTJFrw5MI)
but was advised to better ask the experts in this list. So here we go:
The question is regarding the packs and the repacking of those during
cloning. I'm migr
On Sun, Sep 2, 2012 at 5:07 PM, Enrico Weigelt wrote:
> Hi,
>
>> Would that help ?
>> git help diff
>> [snip]
>> --ignore-space-at-eol
>>Ignore changes in whitespace at EOL.
>>
>>-b, --ignore-space-change
>>Ignore changes in amount of whitespace. This ignores
>
Johannes Sixt writes:
> Am 03.09.2012 21:26, schrieb Junio C Hamano:
>> Nguyễn Thái Ngọc Duy writes:
>>
>>> fetch does printf("%-*s", width, "foo") where "foo" can be an utf-8
>>> string, but width is bytes, not letters. This results in misaligned
>>> ref summary table.
>>
>> "but width is by
Marco Stornelli writes:
> I tried the Johannes's script, but it seems it doesn't work well with
> the pattern of format-patch (To: ,\n ,\n
> ). The multilines are not well managed.
I am guessing that the reason why Jonahhes's "copy our headers out
with continuation lines intact" approach does
> From: Junio C Hamano [mailto:gits...@pobox.com]
> Sent: Monday, September 03, 2012 9:03 PM
> To: Joachim Schmitz
> Cc: git@vger.kernel.org; 'Johannes Sixt'
> Subject: Re: [PATCH 1/2] Support for setitimer() on platforms lacking it
>
> "Joachim Schmitz" writes:
>
> >> > if (!value ) {
> >>
> >
Am 03.09.2012 21:26, schrieb Junio C Hamano:
> Nguyễn Thái Ngọc Duy writes:
>
>> fetch does printf("%-*s", width, "foo") where "foo" can be an utf-8
>> string, but width is bytes, not letters. This results in misaligned
>> ref summary table.
>
> "but width is bytes, not letters" is a misleading
Nguyen Thai Ngoc Duy writes:
> On Mon, Sep 3, 2012 at 8:42 PM, Angelo Borsotti
> wrote:
>> $ git checkout 94d8 -- *
>> $ ls
>> f1
>>
>> Note that the work directory is empty when the checkout is done, and
>> that the checkout restores f1
>> in it, a file that is not denoted by the * pathspec.
>
Nguyễn Thái Ngọc Duy writes:
> fetch does printf("%-*s", width, "foo") where "foo" can be an utf-8
> string, but width is bytes, not letters. This results in misaligned
> ref summary table.
"but width is bytes, not letters" is a misleading statement.
Be careful about three different quantities
"Joachim Schmitz" writes:
>> >if (!value ) {
>>
>> Style: space before ')'?
>
> Will fix.
>
>> >errno = EFAULT;
>> >return -1;
>>
>> EFAULT is good ;-)
>
> That's what 'man setitimer()' on Linux says to happen if invalid value is
> found.
>
>> The emulation in m
Johannes Sixt writes:
> Am 03.09.2012 11:31, schrieb Joachim Schmitz:
>>
>> Hmm, I see that there the errors are handled differently, like this:
>>
>> if (ovalue != NULL)
>> return errno = EINVAL,
>> error("setitimer param 3 != NULL not implemente
Am 03.09.2012 11:31, schrieb Joachim Schmitz:
>
> Hmm, I see that there the errors are handled differently, like this:
>
> if (ovalue != NULL)
> return errno = EINVAL,
> error("setitimer param 3 != NULL not implemented");
>
> Should this be done in
On 29/08/2012 22:16, Dun Peal wrote:
Hi,
I am getting this error every time I pull. All the following have been
executed, but failed to remove this warning:
git prune
git prune --expire now
git gc
git gc --aggressive
What should I do?
Was the error prefixed by 'remote:' (i.e. was it an error
The current script has got the following problems:
1) It doesn't work if the language used by Thunderbird is not English;
2) The field To: filled by format-patch is not evaluated;
3) The field Cc: is loaded from Cc used in the commit message
instead of using the Cc field filled by format-patch in
Il 02/09/2012 22:42, Junio C Hamano ha scritto:
Marco Stornelli writes:
Il 01/09/2012 15:59, Johannes Sixt ha scritto:
Look how you write:
perl -e '... $ENV{'PATCHTMP'} ...'
That is, perl actually sees this script:
... $ENV{PATCHTMP} ...
(no quotes around PATCHTMP). That my be pe
Angelo Borsotti writes:
[please keep it in the list]
> Hi Carlos,
>
> the behavior is quite clear, but the man pages do not describe it properly.
> The man pages state:
>
> "It updates the named paths in the working tree from the index file or
> from a named ...".
>
> In my example, the
Hi,
> Without a command-line onto the filesystem (either local or NFS), how
> do you create a new repository for a new project?
These things are out of the scope of git itself, they belong to another
layer - you're probably looking for some repo hosting solution.
One already was mentioned: gitol
On Mon, Sep 3, 2012 at 7:38 PM, Konstantin Khomoutov
wrote:
> On Mon, 3 Sep 2012 14:07:48 +0100 (BST)
> Mark Hills wrote:
>
> [...]
>> > But I'm actually more curious about why you need this in the first
>> > place, there's a bunch of devs where I work as well, but they never
>> > have the need t
On Mon, 3 Sep 2012 14:07:48 +0100 (BST)
Mark Hills wrote:
[...]
> > But I'm actually more curious about why you need this in the first
> > place, there's a bunch of devs where I work as well, but they never
> > have the need to create new repos on some NFS drive in this manner.
>
> Without a com
On Mon, Sep 3, 2012 at 8:42 PM, Angelo Borsotti
wrote:
> $ git checkout 94d8 -- *
> $ ls
> f1
>
> Note that the work directory is empty when the checkout is done, and
> that the checkout restores f1
> in it, a file that is not denoted by the * pathspec.
I think in this case '*' remains unexpanded
Angelo Borsotti writes:
> Hello,
>
> the man page of git checkout states:
>
> git checkout [-p|--patch] [] [--] ...
>
> It updates the named paths in the working tree from the index file or
> from a named ...
>
> This means that for each file denoted by pathspec, git tries to
> restore it from t
On Mon, Sep 3, 2012 at 6:45 PM, Mark Hills wrote:
> On Mon, 3 Sep 2012, Sitaram Chamarty wrote:
>
>> On Mon, Sep 3, 2012 at 5:17 PM, Konstantin Khomoutov
>> wrote:
>> > On Mon, 3 Sep 2012 11:21:43 +0100 (BST)
>> > Mark Hills wrote:
>>
>> [snip]
>>
>> >> This is quite cumbersome; we have a large
On Mon, 3 Sep 2012, Sitaram Chamarty wrote:
> On Mon, Sep 3, 2012 at 5:17 PM, Konstantin Khomoutov
> wrote:
> > On Mon, 3 Sep 2012 11:21:43 +0100 (BST)
> > Mark Hills wrote:
>
> [snip]
>
> >> This is quite cumbersome; we have a large team of devs who use a
> >> simple 'git clone' to an NFS dir
On Mon, 3 Sep 2012, Ævar Arnfjörð Bjarmason wrote:
> On Mon, Sep 3, 2012 at 12:21 PM, Mark Hills wrote:
> > How do I clone a repo _to_ a new repo over SSH? I tried:
> >
> > cd xx
> > git clone --bare . gitserver:/scm/xx.git
> > git clone --bare . ssh://gitserver/scm/xx.git
> >
> > This does
On Mon, Sep 3, 2012 at 5:17 PM, Konstantin Khomoutov
wrote:
> On Mon, 3 Sep 2012 11:21:43 +0100 (BST)
> Mark Hills wrote:
[snip]
>> This is quite cumbersome; we have a large team of devs who use a
>> simple 'git clone' to an NFS directory, but we wish to retire NFS
>> access.
[snip]
> gitolit
On Mon, 3 Sep 2012 11:21:43 +0100 (BST)
Mark Hills wrote:
> How do I clone a repo _to_ a new repo over SSH? I tried:
>
> cd xx
> git clone --bare . gitserver:/scm/xx.git
> git clone --bare . ssh://gitserver/scm/xx.git
>
> This does not have the expected result, and instead a local path of
On Mon, Sep 3, 2012 at 12:21 PM, Mark Hills wrote:
> How do I clone a repo _to_ a new repo over SSH? I tried:
>
> cd xx
> git clone --bare . gitserver:/scm/xx.git
> git clone --bare . ssh://gitserver/scm/xx.git
>
> This does not have the expected result, and instead a local path of the
> giv
fetch does printf("%-*s", width, "foo") where "foo" can be an utf-8
string, but width is bytes, not letters. This results in misaligned
ref summary table.
Introduce gettext_length() function that returns the string length in
letters. Make the code use TRANSPORT_SUMMARY(x) where the length is
compe
How do I clone a repo _to_ a new repo over SSH? I tried:
cd xx
git clone --bare . gitserver:/scm/xx.git
git clone --bare . ssh://gitserver/scm/xx.git
This does not have the expected result, and instead a local path of the
given name is created (eg. a 'gitserver:' directory)
This seems to
2012/9/2 Junio C Hamano :
> Marco Stornelli writes:
>
>> Il 01/09/2012 15:59, Johannes Sixt ha scritto:
>>
>>> Look how you write:
>>>
>>>perl -e '... $ENV{'PATCHTMP'} ...'
>>>
>>> That is, perl actually sees this script:
>>>
>>>... $ENV{PATCHTMP} ...
>>>
>>> (no quotes around PATCHTMP). T
> From: Junio C Hamano [mailto:gits...@pobox.com]
> Sent: Sunday, September 02, 2012 10:44 PM
> To: Joachim Schmitz
> Cc: git@vger.kernel.org; Johannes Sixt
> Subject: Re: [PATCH 1/2] Support for setitimer() on platforms lacking it
>
> "Joachim Schmitz" writes:
>
> >> > > Should we leave tv_usec
35 matches
Mail list logo
