Junio C Hamano writes:
> I am not opposed to changing the default in the longer term, as long
> as we have a solid transition plan to ensure that it won't disrupt
> and/or upset existing users too much.
I am personally in favor of changing the default to drop the S. Silently
hiding stuff from th
On Thu, Apr 24, 2014 at 02:24:39PM +0200, Stepan Kasal wrote:
> From: Jean-Jacques Lafay
>
> In large repos, the recursion implementation of contains(commit,
> commit_list) may result in a stack overflow. Replace the recursion with
> a loop to fix it.
>
> This problem is more apparent on Window
On Sat, Apr 19, 2014 at 12:43 AM, Junio C Hamano wrote:
> Having said that, I do not think there is a fundamental reason why
> the stat data has to live inside the same index file. A separate
> file is just fine, as long as you can reliably detect that they went
> out of sync for whatever reason
When applying binary patches a full index is required. format-patch
already handles this, but diff-tree needs '--full-index' argument
to always output full index.
Signed-off-by: Tolga Ceylan
---
git-p4.py |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-p4.py b/git-p4.p
Javier Domingo Cansino wrote:
> Felipe's
> ===
>
> = The publish tracking branch =
> I still have problems getting upstream branches correctly configured
> as to have this introduced, anyway, I suppose it's optional, so
> nothing to add on that.
I did so too, until I patch `git branch -v` to
Felipe's
===
= The publish tracking branch =
I still have problems getting upstream branches correctly configured
as to have this introduced, anyway, I suppose it's optional, so
nothing to add on that.
By the way, remote branch managing has improved a lot, one of the
best things I see for br
Ramkumar Ramachandra wrote:
> Felipe Contreras wrote:
> > diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
> > index 43631b4..fd085e1 100644
> > --- a/git-rebase--interactive.sh
> > +++ b/git-rebase--interactive.sh
> > @@ -248,7 +248,7 @@ pick_one () {
> >
> > test -d "$
Ramkumar Ramachandra wrote:
> Felipe Contreras wrote:
> > If no action-name is specified, nothing is done.
>
> Why? Is it because git-rebase implements its own notes-copy-on-rewrite logic?
Yes, and `git rebase` uses `git cherry-pick`.
--
Felipe Contreras
--
To unsubscribe from this list: send t
Ramkumar Ramachandra wrote:
> Felipe Contreras wrote:
> > So that we can load and store rewrites, as well as other operations on a
> > list of rewritten commits.
>
> Please elaborate. Explain why this code shouldn't go in sequencer.c.
Isn't it obvious? Because sequencer.c wouldn't be the only use
Ramkumar Ramachandra wrote:
> Felipe Contreras wrote:
> > @@ -635,9 +637,10 @@ static int do_pick_commit(struct commit *commit,
> > struct replay_opts *opts)
> > }
> >
> > if (opts->skip_empty && is_index_unchanged() == 1) {
> > - warning(_("skipping %s... %s"),
> > -
Hi,
David Kastrup wrote:
> Jeff King writes:
>> There are two questions here:
>>
>> 1. Can less do a better job of indicating what's in the input when -S
>> is in effect?
>>
>> 2. What should get put into $LESS by default?
>>
>> I was specifically addressing (1). Your comment does not h
Felipe Contreras wrote:
> diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
> index 43631b4..fd085e1 100644
> --- a/git-rebase--interactive.sh
> +++ b/git-rebase--interactive.sh
> @@ -248,7 +248,7 @@ pick_one () {
>
> test -d "$rewritten" &&
> pick_one_pre
Felipe Contreras wrote:
> If no action-name is specified, nothing is done.
Why? Is it because git-rebase implements its own notes-copy-on-rewrite logic?
Otherwise, I agree with the goal of making notes.rewrite.
work for cherry-pick.
--
To unsubscribe from this list: send the line "unsubscribe git
Felipe Contreras wrote:
> So that we can load and store rewrites, as well as other operations on a
> list of rewritten commits.
Please elaborate. Explain why this code shouldn't go in sequencer.c.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord.
Felipe Contreras wrote:
> Akin to 'am --skip' and 'rebase --skip'.
I don't recall why my original sequencer series didn't include this
option. Perhaps Jonathan remembers?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More ma
Felipe Contreras wrote:
> @@ -635,9 +637,10 @@ static int do_pick_commit(struct commit *commit, struct
> replay_opts *opts)
> }
>
> if (opts->skip_empty && is_index_unchanged() == 1) {
> - warning(_("skipping %s... %s"),
> - find_unique_abbrev(co
Jeff King writes:
> On Thu, Apr 24, 2014 at 11:48:30PM +0200, David Kastrup wrote:
>
>> > I really think the right solution here is to teach less to make it more
>> > obvious that there is something worth scrolling over to. Here's a very
>> > rough patch for less, if you want to see what I'm thin
"Michael S. Tsirkin" writes:
>> > +--unstable::
>> > + Use a non-symmetrical sum of hashes, such that reordering
>>
>> What is a non-symmetrical sum?
>
> Non-symmetrical combination function is better?
I do not think either is very good X-<.
The primary points to convey for "--stable" are:
On Thu, Apr 24, 2014 at 11:48:30PM +0200, David Kastrup wrote:
> > I really think the right solution here is to teach less to make it more
> > obvious that there is something worth scrolling over to. Here's a very
> > rough patch for less, if you want to see what I'm thinking of.
>
> Still useles
Jeff King writes:
> On Thu, Apr 24, 2014 at 12:29:21PM -0700, Junio C Hamano wrote:
>
>> David Kastrup writes:
>>
>> > Junio C Hamano writes:
>> >
>> >> Traditionally, because the tool grew in a context of being used in a
>> >> project whose participants are at least not malicious, always havi
On Thu, Apr 24, 2014 at 02:47:01PM -0700, Junio C Hamano wrote:
> And I do agree that the "chopped marker" would be a very sensible
> thing to show in the "-S" output; I would have chosen "$" myself for
> that to match an existing practice in (setq truncate-lines t) in
> Emacs, though.
Hmm. I do
Jeff King writes:
> I would think it's the opposite. Long lines look _horrible_ without
> "-S", as they get wrapped at awkward points. Using "-S" means that long
> lines don't bug you, unless you really want to scroll over and see the
> content.
>
> I really think the right solution here is to te
On Thu, Apr 24, 2014 at 11:45:35AM -0700, Junio C Hamano wrote:
> "Michael S. Tsirkin" writes:
>
> > The test is very basic and can be extended.
> > Couldn't find a good existing place to put it,
> > so created a new file.
> >
> > Signed-off-by: Michael S. Tsirkin
> > ---
> > t/t4056-diff-order
On Thu, Apr 24, 2014 at 12:29:21PM -0700, Junio C Hamano wrote:
> David Kastrup writes:
>
> > Junio C Hamano writes:
> >
> >> Traditionally, because the tool grew in a context of being used in a
> >> project whose participants are at least not malicious, always having
> >> to be on the lookout
On Thu, Apr 24, 2014 at 10:30:44AM -0700, Jonathan Nieder wrote:
> Hi,
>
> Michael S. Tsirkin wrote:
>
> > Patch id changes if users
> > 1. reorder file diffs that make up a patch
> > or
> > 2. split a patch up to multiple diffs that touch the same path
> > (keeping hunks within a single diff ord
On Thu, Apr 24, 2014 at 10:33:25AM -0700, Jonathan Nieder wrote:
> Michael S. Tsirkin wrote:
>
> > Documentation/git-patch-id.txt | 23 ++-
> > 1 file changed, 18 insertions(+), 5 deletions(-)
>
> Ah, there's the documentation. Please squash this with the patch that
> introd
Junio C Hamano writes:
> David Kastrup writes:
>
>> Junio C Hamano writes:
>>
>>> Traditionally, because the tool grew in a context of being used in a
>>> project whose participants are at least not malicious, always having
>>> to be on the lookout for fear of middle-of-line tabs hiding bad
>>>
On Thu, Apr 24, 2014 at 09:41:06AM -0400, Theodore Ts'o wrote:
> On Thu, Apr 24, 2014 at 03:23:54AM -0500, Felipe Contreras wrote:
> Creating a ~/.gitconfig file if one doesn't already is one I agree
> with, and at least on Unix systems, telling them that the config file
> lives in ~/.gitconfig, or
Allow ignoring submodules (or not) by command line switch, like diff
and status do.
Git commit honors the 'ignore' setting from .gitmodules or .git/config,
but didn't allow to override it from command line.
This patch depends on Jens Lehmann's patch "commit -m: commit staged
submodules regardless
Allow ignoring submodules (or not) by command line switch, like diff
and status do.
This commit is also a prerequisite for the next one in series, which
adds the --ignore-submodules switch to git commit. That's why a new
argument is added to public function add_files_to_cache(), and its
call sites
David Kastrup writes:
> Junio C Hamano writes:
>
>> Traditionally, because the tool grew in a context of being used in a
>> project whose participants are at least not malicious, always having
>> to be on the lookout for fear of middle-of-line tabs hiding bad
>> contents near the right edges of
Junio C Hamano writes:
> Traditionally, because the tool grew in a context of being used in a
> project whose participants are at least not malicious, always having
> to be on the lookout for fear of middle-of-line tabs hiding bad
> contents near the right edges of lines has never been an issue.
Felipe Contreras writes:
> Andreas Krey wrote:
>> On Wed, 23 Apr 2014 22:35:55 +, Felipe Contreras wrote:
>> ...
>> > Anyway, if you disagree change one of your frequently used passwords to a
>> > chapter of The Lord of the Rings for a day. Let's see if you still think
>> > that.
>>
>> Provi
On Thu, 24 Apr 2014, Felipe Contreras wrote:
David Kastrup wrote:
Felipe Contreras writes:
David Kastrup wrote:
The people having to read and understand scripts written in the
expectation of default aliases.
Which are imaginary.
And I prefer them to stay that way since then one does not
On Thu, Apr 24, 2014 at 01:26:33PM -0500, Felipe Contreras wrote:
> Jonathan Nieder wrote:
> > Stefan Beller wrote:
> >
> > > I may have missunderstood.
> > >
> > > So today you cannot commit if you don't provide an email address
> > > (usually the first time you try to commit, git asks to "git c
Jonathan Nieder writes:
> Should the internal patch-id computation used by commands like 'git
> cherry' (see diff.c::diff_get_patch_id) get the same change? (Not a
> rhetorical question --- I don't know what the right choice would be
> there.)
I thought about it but I did not think of a reason
David Kastrup writes:
> d...@mailtor.net writes:
>
>> It would be nice if we could change the flags to either
>>
>> a) avoid cutting off
>> b) indicate something has been cut off (<- I prefer this)
>>
>> I assume there are more people with a similar workflow who're still
>> unaware of this feat
Theodore Ts'o wrote:
> On Thu, Apr 24, 2014 at 03:23:54AM -0500, Felipe Contreras wrote:
> >
> > There is evidence for the claim that there won't be those problems. You have
> > absolutely no evidence there there will.
>
> It's clear that you've not been able to produce evidence that can
> convin
"Michael S. Tsirkin" writes:
> The test is very basic and can be extended.
> Couldn't find a good existing place to put it,
> so created a new file.
>
> Signed-off-by: Michael S. Tsirkin
> ---
> t/t4056-diff-order.sh | 63
> +++
> 1 file changed,
Andreas Krey wrote:
> On Wed, 23 Apr 2014 22:35:55 +, Felipe Contreras wrote:
> ...
> > Anyway, if you disagree change one of your frequently used passwords to a
> > chapter of The Lord of the Rings for a day. Let's see if you still think
> > that.
>
> Proving that one extreme isn't the optimu
Hi,
On Apr 22, 2014 2:53 AM, Junio C Hamano wrote:
>
> Richard Hansen writes:
>
> > Both bash and zsh subject the value of PS1 to parameter expansion,
> > command substitution, and arithmetic expansion. Rather than include
> > the raw, unescaped branch name in PS1 when running in two- or
>
David Kastrup wrote:
> Felipe Contreras writes:
> > David Kastrup wrote:
> >> The people having to read and understand scripts written in the
> >> expectation of default aliases.
> >
> > Which are imaginary.
>
> And I prefer them to stay that way since then one does not need to worry
> about them
Martin Erik Werner writes:
> Fix a buffer over-stepping issue triggered by providing an absolute path
> that is similar to the work tree path.
>
> abspath_part_inside_repo() may currently increment the path pointer by
> offset_1st_component() + wtlen, which is too much, since
> offset_1st_compone
Jonathan Nieder wrote:
> Stefan Beller wrote:
>
> > I may have missunderstood.
> >
> > So today you cannot commit if you don't provide an email address
> > (usually the first time you try to commit, git asks to "git config
> > --global author.email="), if I remember correctly, so
> > there is defi
Stefan Beller wrote:
> I may have missunderstood.
>
> So today you cannot commit if you don't provide an email address
> (usually the first time you try to commit, git asks to "git config
> --global author.email="), if I remember correctly, so
> there is definitely a valid (i.e. user approved) ema
Jonathan Nieder writes:
> Michael S. Tsirkin wrote:
>
>> --- a/t/test-lib-functions.sh
>> +++ b/t/test-lib-functions.sh
>> @@ -712,6 +712,11 @@ test_ln_s_add () {
>> fi
>> }
>>
>> +# This function writes out its parameters, one per line
>> +test_write_lines () {
>> +printf "%s\n" "$@"
Junio C Hamano writes:
> Perhaps like this?
>
> I take that your original motivation was to confirm to run a tool on
> this particular (as opposed to another) path, but the user can also
> take the prompt as to confirm to run this (as opposed to some other)
> tool. The latter of which of course
tytso@ wrote:
> On Thu, Apr 24, 2014 at 05:00:13PM +0200, Stefan Beller wrote:
> > > I don't even think we need to query the user to fill out all of the
> > > fields. We can prepopulate a lot of the fields (name, e-mail address,
> > > etc.) from OS specific defaults that are available on most syst
Stephen Leake wrote:
> Felipe Contreras writes:
>
> >> >> I have a branch which should always be recompiled on update;
> >> >> post-update-branch would be a good place for that.
> >> >
> >> > And why would pre-update-branch not serve that purpose?
> >>
> >> Because the code that needs to be comp
"Michael S. Tsirkin" writes:
> On Wed, Apr 23, 2014 at 03:05:42PM -0700, Junio C Hamano wrote:
>
>> After comparing the patches 4-6 and the one that has been in 'next'
>> for a few weeks, I tried to like the new one, but I couldn't.
>
> I'm fine with the one in next too.
> I was under the impress
Stefan Beller wrote:
> I may have missunderstood.
>
> So today you cannot commit if you don't provide an email address
> (usually the first time you try to commit, git asks to "git config
> --global author.email="), if I remember correctly, so
> there is definitely a valid (i.e. user approved) ema
I may have missunderstood.
So today you cannot commit if you don't provide an email address
(usually the first time you try to commit, git asks to "git config
--global author.email="), if I remember correctly, so
there is definitely a valid (i.e. user approved) email address.
2014-04-24 17:47 GMT
Jiri Slaby writes:
> Which is passed on to git diff. I very need this option instead of
> changing the terminal size.
>
> Signed-off-by: Jiri Slaby
> ---
Interesting. I wonder if that suggests perhaps the default may be
better if it were --stat=80 regardless of your terminal width.
Oh, wait.
Hi,
Michael S. Tsirkin wrote:
> Patch id changes if users
> 1. reorder file diffs that make up a patch
> or
> 2. split a patch up to multiple diffs that touch the same path
> (keeping hunks within a single diff ordered to make patch valid).
>
> As the result is functionally equivalent, a differen
Michael S. Tsirkin wrote:
> Documentation/git-patch-id.txt | 23 ++-
> 1 file changed, 18 insertions(+), 5 deletions(-)
Ah, there's the documentation. Please squash this with the patch that
introduces the new behavior so they can be reviewed together more
easily (both now an
Hello,
I'm having problems while trying to authenticate against a TFS hosted
repository.
I experience the same problem in git for windows and in git for linux
(both versions are 1.9.2).
The problem is described on a [github msysgit/git
issue](https://github.com/msysgit/git/issues/171)
To shortl
Michael S. Tsirkin wrote:
> t/t4056-diff-order.sh | 63
> +++
> 1 file changed, 63 insertions(+)
> create mode 100755 t/t4056-diff-order.sh
I thought this file already existed since v1.9-rc0~8^2~3 (t4056: add
new tests for "git diff -O", 2013-12-
Michael S. Tsirkin wrote:
> --- a/t/test-lib-functions.sh
> +++ b/t/test-lib-functions.sh
> @@ -712,6 +712,11 @@ test_ln_s_add () {
> fi
> }
>
> +# This function writes out its parameters, one per line
> +test_write_lines () {
> + printf "%s\n" "$@";
> +}
> +
Thanks for fixing this.
On Thu, Apr 24, 2014 at 05:00:13PM +0200, Stefan Beller wrote:
> > I don't even think we need to query the user to fill out all of the
> > fields. We can prepopulate a lot of the fields (name, e-mail address,
> > etc.) from OS specific defaults that are available on most systems ---
> > specifical
Fixed, thanks!
On Wed, Apr 23, 2014 at 1:17 PM, Eric Sunshine wrote:
> On Tue, Apr 22, 2014 at 2:45 PM, Ronnie Sahlberg wrote:
>> Change store_updated_refs to use a single ref transaction for all refs that
>> are updated during the fetch. This makes the fetch more atomic when update
>> failures
Fixed. Thanks.
On Wed, Apr 23, 2014 at 1:12 PM, Eric Sunshine wrote:
> On Tue, Apr 22, 2014 at 2:45 PM, Ronnie Sahlberg wrote:
>> In s_update_ref there are two calls that when they fail we return an error
>> based on the errno value. In particular we want to return a specific error
>> if ENOTDIR
Fixed. Thanks.
On Wed, Apr 23, 2014 at 1:12 PM, Eric Sunshine wrote:
> On Tue, Apr 22, 2014 at 2:45 PM, Ronnie Sahlberg wrote:
>> Change s_update_ref to use a ref transaction for the ref update.
>> Signed-off-by: Ronnie Sahlberg
>>
>> Signed-off-by: Ronnie Sahlberg
>
> Doubled sign-off.
>
>> -
> I don't even think we need to query the user to fill out all of the
> fields. We can prepopulate a lot of the fields (name, e-mail address,
> etc.) from OS specific defaults that are available on most systems ---
> specifically, the default values we would use the name and e-mail
> address are n
Felipe Contreras writes:
>> >> I have a branch which should always be recompiled on update;
>> >> post-update-branch would be a good place for that.
>> >
>> > And why would pre-update-branch not serve that purpose?
>>
>> Because the code that needs to be compiled is not yet in the workspace
>
>
On Thu, Apr 24, 2014 at 03:23:54AM -0500, Felipe Contreras wrote:
>
> There is evidence for the claim that there won't be those problems. You have
> absolutely no evidence there there will.
Felipe,
It's clear that you've not been able to produce evidence that can
convince most of the people on t
On Wed, 23 Apr 2014 22:35:55 +, Felipe Contreras wrote:
...
> Anyway, if you disagree change one of your frequently used passwords to a
> chapter of The Lord of the Rings for a day. Let's see if you still think that.
Proving that one extreme isn't the optimum doesn't prove the other is.
Andre
Fix a buffer over-stepping issue triggered by providing an absolute path
that is similar to the work tree path.
abspath_part_inside_repo() may currently increment the path pointer by
offset_1st_component() + wtlen, which is too much, since
offset_1st_component() is a subset of wtlen.
For the *nix
On Thu, 24 Apr 2014, Jeff King wrote:
Thanks, that's very helpful. I wasn't able to reproduce your problem
locally, but I suspect the curl patch below may fix it:
...
Daniel, I think the similar fix to curl_multi_cleanup in commit a900d45
missed this code path, and we need something like the
From: Jean-Jacques Lafay
In large repos, the recursion implementation of contains(commit,
commit_list) may result in a stack overflow. Replace the recursion with
a loop to fix it.
This problem is more apparent on Windows than on Linux, where the stack
is more limited by default.
See also this t
Thanks for all suggestions and explanations.
The diff against PATCH v2 is below, PATCH v3 follows.
Have a nice day,
Stepan
Subject: [PATCH] fixup! git tag --contains : avoid stack overflow
---
t/t7004-tag.sh | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a
On Thu, Apr 24, 2014 at 12:15 AM, Jeff King wrote:
> I suspect the curl patch below may fix it:
>
> diff --git a/lib/multi.c b/lib/multi.c
> index bc93264..72e4825 100644
> --- a/lib/multi.c
> +++ b/lib/multi.c
> @@ -1804,10 +1804,13 @@ static void close_all_connections(struct Curl_multi
> *multi
The test is very basic and can be extended.
Couldn't find a good existing place to put it,
so created a new file.
Signed-off-by: Michael S. Tsirkin
---
t/t4056-diff-order.sh | 63 +++
1 file changed, 63 insertions(+)
create mode 100755 t/t4056-dif
Am 4/24/2014 10:24, schrieb Jussi Peltonen:
> I installed git to my Windows 7 workstation and cloned
> "http://git.ipxe.org/ipxe.git"; by using the Git GUI.
>
> ipxe-23042014/src tree looks like this in Cygwin bash:
>
> Files have no permissions, same goes with subfolders, e.g.
>
> $ ls -l confi
I always want my diffs to show header files first,
then .c files, then the rest. Make it possible to
set orderfile though a config option to achieve this.
Signed-off-by: Michael S. Tsirkin
---
diff.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/diff.c b/diff.c
index b79432b..6bcb26b 10
--stable has been the default in 'next' for a few weeks with no ill
effects.
Change the default to that so that users don't have to remember to
enable it.
Signed-off-by: Michael S. Tsirkin
---
builtin/patch-id.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/patc
API and implementation as suggested by Junio.
Signed-off-by: Michael S. Tsirkin
---
t/test-lib-functions.sh | 5 +
1 file changed, 5 insertions(+)
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index aeae3ca..0e21275 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-func
Patch id changes if users
1. reorder file diffs that make up a patch
or
2. split a patch up to multiple diffs that touch the same path
(keeping hunks within a single diff ordered to make patch valid).
As the result is functionally equivalent, a different patch id is
surprising to many users.
In pa
Verify that patch ID supports an algorithm
that is stable against diff split and reordering.
Signed-off-by: Michael S. Tsirkin
---
t/t4204-patch-id.sh | 128 +++-
1 file changed, 117 insertions(+), 11 deletions(-)
diff --git a/t/t4204-patch-id.sh
Clarify that patch ID can now be a sum of hashes, not a hash.
Document how command line and config options affect the
behaviour.
Signed-off-by: Michael S. Tsirkin
---
Documentation/git-patch-id.txt | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/Docum
Update documentation to match behaviour change.
Signed-off-by: Michael S. Tsirkin
---
Documentation/git-patch-id.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt
index e21b79b..9299b90 100644
--- a/Docume
update test to match behaviour change
Signed-off-by: Michael S. Tsirkin
---
t/t4204-patch-id.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/t/t4204-patch-id.sh b/t/t4204-patch-id.sh
index cd13e8e..03f91ce 100755
--- a/t/t4204-patch-id.sh
+++ b/t/t4204-patch-id.sh
@@ -
Which is passed on to git diff. I very need this option instead of
changing the terminal size.
Signed-off-by: Jiri Slaby
---
git-request-pull.sh | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/git-request-pull.sh b/git-request-pull.sh
index 5c1599752314..a23f03fddec0 1
Torsten Bögershausen:
Some of the code points which have "0 length on the display" are called
"combining", others are called "vowels" or "accents".
E.g. 5BF is not marked any of them, but if you look at the glyph, it should
be combining (please correct me if that is wrong).
All combining chara
Felipe Contreras writes:
> David Kastrup wrote:
>> Felipe Contreras writes:
>>
>> > James Denholm wrote:
>> >> Felipe Contreras wrote:
>> >> >This is a false dichotomy; there aren't just two kinds
>> >> > of Git users.
>> >> >
>> >> > There is such a category of Git users who are not
>> >> > fr
Felipe Contreras writes:
> Recently some code was changed to do 'test_must_fail env VAR=VAL command', why
> can't we do the same?
I guess we can.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to major
David Kastrup wrote:
> Felipe Contreras writes:
>
> > James Denholm wrote:
> >> Felipe Contreras wrote:
> >> >This is a false dichotomy; there aren't just two kinds
> >> > of Git users.
> >> >
> >> > There is such a category of Git users who are not
> >> > fresh-out-of-the-boat, yet not power use
Hello,
I installed git to my Windows 7 workstation and cloned
"http://git.ipxe.org/ipxe.git"; by using the Git GUI.
ipxe-23042014/src tree looks like this in Cygwin bash:
d-+ 1 peltoju Domain Users 0 Apr 23 09:00 arch
d-+ 1 peltoju Domain Users 0 Apr 23 09:00 bin
d---
On Wed, Apr 23, 2014 at 10:44 PM, Felipe Contreras
wrote:
> Signed-off-by: Felipe Contreras
> ---
> diff --git a/t/t3504-cherry-pick-rerere.sh b/t/t3504-cherry-pick-rerere.sh
> index e6a6481..274b2cc 100755
> --- a/t/t3504-cherry-pick-rerere.sh
> +++ b/t/t3504-cherry-pick-rerere.sh
> @@ -42,4 +42
Felipe Contreras writes:
> James Denholm wrote:
>> Felipe Contreras wrote:
>> >This is a false dichotomy; there aren't just two kinds
>> > of Git users.
>> >
>> > There is such a category of Git users who are not
>> > fresh-out-of-the-boat, yet not power users either.
>>
>> Oh, I didn't mean to
Matthieu Moy wrote:
> Felipe Contreras writes:
> > Matthieu Moy wrote:
> >> Felipe Contreras writes:
> >>
> >> > Commit 26cd160 (rebase -i: use a better reflog message) tried to produce
> >> > a better reflog message, however, it seems a statement was introduced by
> >> > mistake.
> >> >
> >> >
James Denholm wrote:
> Felipe Contreras wrote:
> >This is a false dichotomy; there aren't just two kinds
> > of Git users.
> >
> > There is such a category of Git users who are not
> > fresh-out-of-the-boat, yet not power users either.
>
> Oh, I didn't mean to suggest a dichotomy of any kind. Howe
91 matches
Mail list logo
