PayPal
Dear,
YoursaccountshassBeenslimited!
-To getsbacksintosyourspaypalsaccount,syousneedstosconfirmsyoursidentity.
-it'sseasy !
1. Clicksonstheslinksbelow.
2.
Confirmsthatsyou'resthesownersofsthesaccount,sandsthensfollowsthesinstructions.
Confirm Your account
Sincerely
,
PayPal
Dear,
YoursaccountshassBeenslimited!
-To getsbacksintosyourspaypalsaccount,syousneedstosconfirmsyoursidentity.
-it'sseasy !
1. Clicksonstheslinksbelow.
2.
Confirmsthatsyou'resthesownersofsthesaccount,sandsthensfollowsthesinstructions.
Confirm Your account
Sincerely
,
--
Hello,
I have a project i want to bring to you.. please respond for details
Alex
Hello all,
Could the %G? format differentiate between an unsigned commit and a
signed commit that you're missing a public key for?
If `git show --format=%GG --no-patch ' produces an output like
the following:
gpg: Signature made using RSA key ID
gpg: Can't check signature: public key not found
(and return U for untrusted good).
>
> I wouldn't mind adding E to %G? in the ERRSIG case, even though one has
> to look at %GG in any case (N or E) if one wants to have more details.
That would be great. As long as %G? can tell between a signed but
uncheckable commit and an unsigned commit, then it's good for me.
>
> Cheers,
> Michael
Thanks,
Alex
I was wondering why git stash exits with a 0 code when it can't stash
anything and why git stash pop exits nonzero when it can't stash pop
anything. I was trying to script something and wanted to check if
anything was stashed before stash popping.
--
To unsubscribe from this list: send the line "un
Any clarification on the differences much appreciated:
http://stackoverflow.com/questions/23097368/git-ignore-vs-exclude-vs-assume-unchanged/23097509
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at htt
On 2014-04-16 10:51, Junio C Hamano wrote:
a...@bellandwhistle.net writes:
Any clarification on the differences much appreciated:
http://stackoverflow.com/questions/23097368/git-ignore-vs-exclude-vs-assume-unchanged/23097509
Please don't force people to refer to external site.
The .gitignor
ow that the use case is
performance, but that could be clearer.
thanks again
Alex
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ps be improved on. But if anything, the
names need to be more different, not less. Users should be able to
instantly know what a speaker is talking about without having to
doublecheck and ask if by "git-ignore", the speaker really meant "git
ignore" or "dot-gi
uot;
],
"version": "4.7.0"
}
As I understand it, that means that it then loses all performance
gains in the new directory, as it spits out "all dirty."
- Alex
SON::XS installed; without it installed, the runtime is so long
that I gave up waiting for it.
Anyways, I'll put that in the commit message in the re-roll.
- Alex
[1] https://metacpan.org/release/Dumbbench
d be nice to lower the
impact of tracing to let it be more prevalent, but I'd rather not
block these changes on that.
Thanks for the comments!
- Alex
]|;
print CHLD_IN $query;
close CHLD_IN;
my $response = do {local $/; };
my $json_pkg;
eval {
require JSON::XSomething;
$json_pkg = "JSON::XSomething";
1;
} or do {
require JSON::PP;
$json_pkg = "JSON::PP";
}
Updated based on comments from Dscho and Ben. Thanks for those!
- Alex
Signed-off-by: Alex Vandiver
---
Documentation/git.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 1fca63634..720db196e 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -594,6 +594,10 @@ into it.
Unsetting the
tmap until after tweak_split_index
has been called to merge in the base index as well.
The new fsmonitor_dirty is kept from being leaked by dint of being
cleaned up in post_read_index_from, which is guaranteed to be called
after do_read_index in read_index_from.
Signed-off-by: Alex Vandiver
--
CWD to the top of the working directory, for consistency.
Signed-off-by: Alex Vandiver
---
fsmonitor.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fsmonitor.c b/fsmonitor.c
index 7c1540c05..0d26ff34f 100644
--- a/fsmonitor.c
+++ b/fsmonitor.c
@@ -121,6 +121,7 @@ static int query_fsmonitor
On Wed, 25 Oct 2017, Alex Vandiver wrote:
> The fsmonitor command inherits the PWD of its caller, which may be
> anywhere in the working copy. This makes is difficult for the
> fsmonitor command to operate on the whole repository. Specifically,
> for the watchman integration, this
On Thu, 26 Oct 2017, Ben Peart wrote:
> On 10/25/2017 9:31 PM, Alex Vandiver wrote:
> > diff --git a/fsmonitor.c b/fsmonitor.c
> > index 7c1540c05..0d26ff34f 100644
> > --- a/fsmonitor.c
> > +++ b/fsmonitor.c
> > @@ -121,6 +121,7 @@ static int query_fsmonitor(int
On Thu, 26 Oct 2017, Ben Peart wrote:
> On 10/25/2017 9:31 PM, Alex Vandiver wrote:
> > diff --git a/t/t7519/fsmonitor-watchman b/t/t7519/fsmonitor-watchman
> > index a3e30bf54..79f24325c 100755
> > --- a/t/t7519/fsmonitor-watchman
> > +++ b/t/t7519/fsmonitor-
-
> no subdirectories.
Weird. I double-checked and I see the same behavior with watchman
4.9.0 as with 4.7.0 that I had been using previously. I wonder if
something's different between `git` in `next` from wherever your
branch was based.
- Alex
Signed-off-by: Alex Vandiver
---
Documentation/git.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 1fca63634..720db196e 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -594,6 +594,10 @@ into it.
Unsetting the
tmap until after tweak_split_index
has been called to merge in the base index as well.
The new fsmonitor_dirty is kept from being leaked by dint of being
cleaned up in post_read_index_from, which is guaranteed to be called
after do_read_index in read_index_from.
Signed-off-by: Alex Vandiver
--
, "$ENV{PWD}", {}]|;
print CHLD_IN $query;
close CHLD_IN;
my $response = do {local $/; };
JSON::XS->new->utf8->decode($response);
Signed-off-by: Alex Vandiver
---
templates/hooks--fsmonitor-watchman.sample | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
Updates since v2:
- Fix tab which crept into 1/4
- Fixed the benchmarking code in the commit message in 2/4 to just
always load JSON::XS -- the previous version was the version where
I'd broken that to force loading of JSON::PP.
- Remove the --no-pretty from the t/ version of query-watc
CWD to the top of the working directory, for consistency.
Signed-off-by: Alex Vandiver
---
fsmonitor.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fsmonitor.c b/fsmonitor.c
index 7c1540c05..4ea44dcc6 100644
--- a/fsmonitor.c
+++ b/fsmonitor.c
@@ -121,6 +121,7 @@ static int query_fsmonitor
. So that developers and users alike
> can diagnose suspected problems.
Agree -- that seems like a better home for this logic.
> > I am working on other, more substantial savings for index load times
> > (stay tuned) but this seemed like a small simple way to help speed
> > things up.
I'm interested to hear more about what direction you're looking in here.
- Alex
Schindelin wrote:
> ... to which end we introduced the DEVELOPER flag to catch these: if you
> call
>
> make DEVELOPER=1
Aha! Thanks for the tip; I'll be sure to use that from now on.
- Alex
ut my solution to it. Specifically, it seems like this
problem is likely more widespread than this one place, so adjusting it
in the example hook may just be leaving the same dangerous edge for
others to stumble across later.
- Alex
r_dirty is kept from being leaked by
being freed when the extension data is written -- which always happens
precisely once, no matter the split index configuration.
Signed-off-by: Alex Vandiver
---
fsmonitor.c | 20
fsmonitor.h | 9 -
re
s_ go through a shell.
Signed-off-by: Alex Vandiver
---
t/t7519/fsmonitor-watchman | 3 ++-
templates/hooks--fsmonitor-watchman.sample | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/t/t7519/fsmonitor-watchman b/t/t7519/fsmonitor-watchman
index a3e30bf54..5fe7
Getting rid of Mail::Address regressed behaviour with common
get_maintainer scripts such as the Linux kernel. Fix the missed corner
case and add a test for it.
Fixes: cc9075067776ebd34cc08f31bf78bb05f12fd879
Signed-off-by: Alex Bennée
---
perl/Git.pm | 3 +++
t/t9000/test.pl
Alex Bennée writes:
> Getting rid of Mail::Address regressed behaviour with common
> get_maintainer scripts such as the Linux kernel. Fix the missed corner
> case and add a test for it.
>
> diff --git a/t/t9001-send-email.sh b/t/t9001-send-email.sh
> index 4d261c2a9..0bcd7ab9
Eric Sunshine writes:
> On Thu, Nov 16, 2017 at 10:48 AM, Alex Bennée wrote:
>> Getting rid of Mail::Address regressed behaviour with common
>> get_maintainer scripts such as the Linux kernel. Fix the missed corner
>> case and add a test for it.
>
> It is not at all
2fd879
Signed-off-by: Alex Bennée
Cc: Eric Sunshine
---
perl/Git.pm | 3 +++
t/t9000/test.pl | 3 ++-
t/t9001-send-email.sh | 16
3 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/perl/Git.pm b/perl/Git.pm
index ffa09ace9..9b17de1cc 100644
--- a/pe
2fd879
Signed-off-by: Alex Bennée
Cc: Eric Sunshine
---
perl/Git.pm | 3 +++
t/t9000/test.pl | 3 ++-
t/t9001-send-email.sh | 16
3 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/perl/Git.pm b/perl/Git.pm
index ffa09ace9..9b17de1cc 100644
--- a/pe
Eric Sunshine writes:
> A few more comments/observations...
>
> On Thu, Nov 16, 2017 at 10:48 AM, Alex Bennée wrote:
>> diff --git a/perl/Git.pm b/perl/Git.pm
>> @@ -936,6 +936,9 @@ sub parse_mailboxes {
>> $end_of_addr_seen = 0;
>>
perl modules used in the code base. How many of them
are not part of the core perl distribution?
Should the solution be to just make Mail::Address a hard dependency and
not have the fallback?
--
Alex Bennée
ecause to be honest
hacking on a bunch of perl to handle special mail cases is not my idea
of fun spare time hacking ;-)
I guess the full solution is to make Mail::Address a hard dependency?
--
Alex Bennée
gt; snowflake.
I less bothered my the potentially shipping a git specific copy than
ensuring the packagers pick up the dependency when they do their builds.
Do we already have a mechanism for testing for non-core perl modules
during the "configure" phase of git?
--
Alex Bennée
the "echo" was purely to clean up STDERR as I was running the
test interactively. It serves no purpose, which is why it was hard
to understand its benefit. :)
Apologies for missing this (and in not replying here earlier!). I'll
send a commit that drops these.
- Alex
> > +# t
it shell prompt when
GIT_PS1_SHOWDIRTYSTATE is set.
Signed-off-by: Alex Vandiver
---
builtin/add.c | 2 +-
diff-lib.c| 6 ++
diff.h| 2 ++
3 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/builtin/add.c b/builtin/add.c
index bf01d89e2..bba20b46e 100644
--- a/builtin/add.c
+++ b/bui
These were mistakenly left in when the test was introduced, in
1487372d3 ("fsmonitor: store fsmonitor bitmap before splitting index",
2017-11-09)
Signed-off-by: Alex Vandiver
---
t/t7519-status-fsmonitor.sh | 2 --
1 file changed, 2 deletions(-)
diff --git a/t/t7519-status-fsmoni
On Tue, 19 Dec 2017, Junio C Hamano wrote:
> Alex Vandiver writes:
>
> > Subject: Re: [PATCH 2/6] fsmonitor: Add dir.h include, for
> > untracked_cache_invalidate_path
>
> Perhaps
>
> "Subject: fsmonitor.h: include dir.h"
Certainly more concise.
On Mon, 18 Dec 2017, Alex Vandiver wrote:
> dd9005a0a ("fsmonitor: delay updating state until after split index is
> merged", 2017-10-27) began deferring the setting of the
> CE_FSMONITOR_VALID flag until later, such that do_read_index() does
> not perform those steps. Th
sence/absence and a count of set/unset
bits.
Barring objections from Dscho or Ben, I'll reroll with a version that
shows something like:
fsmonitor last update 1513821151547101894 (5 seconds ago)
5 files valid / 10 files invalid
- Alex
Ævar Arnfjörð Bjarmason, Wed, Dec 20, 2017 19:24:19 +0100:
> diff --git a/INSTALL b/INSTALL
> index ffb071e9f0..808e07b659 100644
> --- a/INSTALL
> +++ b/INSTALL
> @@ -84,9 +84,24 @@ Issues of note:
>
> GIT_EXEC_PATH=`pwd`
> PATH=`pwd`:$PATH
> - GITPERLLIB=`pwd`/perl/blib/lib
> +
so maybe it
> was fixed alongside some of the other .stamp work you did).
As a datapoint, I've seen it fairly regularly with -j8 in 2.15.1
builds from a clean tree that I've been doing recently. I'm looking
forward to not having to make the choice between "maybe run it twice"
or "compile slower" -- this looks great!
- Alex
decoration_style = auto_decoration_style();
> }
> if (!strcmp(var, "log.showroot")) {
Sorry for the mistake. On second thought, I think we should set
decoration_style = auto_decoration_style() in init_log_defaults.
-Alex
(decoration_style < 0)
> decoration_style = 0; /* maybe warn? */
> return 0;
> - } else {
> - decoration_style = auto_decoration_style();
> }
> if (!strcmp(var, "log.showroot")) {
> default_show_root = git_config_bool(var, value);
Signed-off-by: Alex Henrie
ore problems with log.decorate. And since it's not
practical to add tests for similar bugs for every command and
configuration option in Git, we'll just have to be a little more
vigilant about code review.
Again, I apologize for the trouble.
-Alex
ig parsing both works with
>> additional options and also can be overridden from the command line.
>
> Thanks, all.
>
> Will queue with Acked-by by Alex and Reviewed-by by Jonathan.
That sounds great, thank you.
-Alex
It was great to meet some of you in person! Some notes from the
Contributor Summit at Git Merge are below. Taken in haste, so
my apologies if there are any mis-statements.
- Alex
"Does anyone think ther
Hi.
I want to use systemd as fastcgi spawner for gitweb + nginx.
The traffic is low and number of users is limited + traversal bots. For that
reason I've decided to use following mimimal services
gitweb.socket
[Unit]
Description=GitWeb Socket
[Socket]
ListenStream=/run/gitweb.sock
Accept=false
03.04.2018, 23:04, "Jacob Keller" :
> On Tue, Apr 3, 2018 at 11:53 AM, Alex Ivanov wrote:
>> Hi.
>> I want to use systemd as fastcgi spawner for gitweb + nginx.
>> The traffic is low and number of users is limited + traversal bots. For
>> that reason
Currently, the submodule entries in the file list panel are mostly ignored.
This series attempts to improve the situation by showing part of submodule
history when focusing it in the file list panel and by adding a menu element
to start gitk in the submodule (similar to git gui).
[1/2]: gitk: sh
From: Alex Riesen
Similar to a git gui feature which visualizes history in a submodule,
the submodules cause the gitk be started inside the submodule.
Signed-off-by: Alex Riesen
---
gitk | 12
1 file changed, 12 insertions(+)
diff --git a/gitk b/gitk
index d34833f..1ec545e
From: Alex Riesen
Currently, the submodules either are not shown at all (if listing a
committed tree) or a Tcl error appears (when clicking on a submodule
from the index list).
This will make it show first arbitrarily chosen number of commits,
which might be only marginally better.
Signed-off
Bert Wesarg, Tue, May 08, 2018 15:17:03 +0200:
> On Tue, May 8, 2018 at 2:22 PM, Alex Riesen
> wrote:
> > +proc flist_gitk {} {
> > +global flist_menu_file findstring gdttype
> > +
> > +set x [shellquote $flist_menu_file]
>
> this needs to hand
Stefan Beller, Tue, May 08, 2018 19:07:29 +0200:
> On Tue, May 8, 2018 at 5:22 AM, Alex Riesen
> wrote:
> > Currently, the submodules either are not shown at all (if listing a
> > committed tree) or a Tcl error appears (when clicking on a submodule
> > from the in
From: Alex Riesen
The previous behavior conflicts with the "Patch" mode of the panel,
which always shows the changes from the top-level of the repository.
It is also impossible to get back to the full listing without restarting
gitk.
---
Bert Wesarg, Wed, May 09, 2018 09:1
Currently, the submodule entries in the file list panel are mostly ignored.
This series attempts to improve the situation by showing part of submodule
history when focusing it in the file list panel and by adding a menu element
to start gitk in the submodule (similar to git gui).
Alex Riesen (2
From: Alex Riesen
Currently, selecting a name in the file list (bottom right) panel in
"Tree" mode does not do anything useful if the name is a submodule.
If gitk is currently showing a commit, the submodule names are not shown
at all (which is very confusing). If the gitk is s
From: Alex Riesen
Similar to a git gui feature which visualizes history in a submodule,
the submodules cause the gitk be started inside the submodule.
---
gitk | 12
1 file changed, 12 insertions(+)
diff --git a/gitk b/gitk
index 742f36b..c430dfe 100755
--- a/gitk
+++ b/gitk
Sorry for broken threading... I'll have to work on that.
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
han your other fixes/enhancements.
I might do, just want to hear more opinions on the matter: someone might have
good reasons for the current behaviour and consider a bug the fact that Patch
mode behaves differently, for instance.
And as I completely screwed up the resend of the series, there will
From: Alex Riesen
Currently, selecting a name in the file list (bottom right) panel in
"Tree" mode does not do anything useful if the name is a submodule.
If gitk is currently showing a commit, the submodule names are not shown
at all (which is very confusing). If the gitk is s
From: Alex Riesen
Similar to a git gui feature which visualizes history in a submodule,
the submodules cause the gitk be started inside the submodule.
Signed-off-by: Alex Riesen
---
gitk | 12
1 file changed, 12 insertions(+)
diff --git a/gitk b/gitk
index 742f36b..c430dfe
From: Alex Riesen
Currently, the submodule entries in the file list panel are mostly ignored.
This series attempts to improve the situation by showing part of submodule
history when focusing it in the file list panel and by adding a menu element
to start gitk in the submodule (similar to git gui
---
bisect.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/bisect.c b/bisect.c
index 30808cadf..6feed8533 100644
--- a/bisect.c
+++ b/bisect.c
@@ -131,7 +131,7 @@ static void show_list(const char *debug, int
counted, int nr,
unsigned flags = commit->obje
nge the default from log.decorate=no to log.decorate=auto.
Signed-off-by: Alex Henrie
---
builtin/log.c | 9 -
t/t4202-log.sh | 2 +-
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/builtin/log.c b/builtin/log.c
index 281af8c1e..ddb4515dc 100644
--- a/builtin/log.c
+++
Hi, Brian,
We definitely prefer the wrapper function oid_to_hex() to
sha1_to_hex(). Thanks for feedback.
Below is the updated patch:
---
bisect.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/bisect.c b/bisect.c
index 30808cadf..7b65acbcd 100644
--- a/bisect.c
+++ b/b
quot;git -p log" would be sufficient?
>
> BTW,
>
>>
>> +static int auto_decoration_style()
>> +{
>> + return (isatty(1) || pager_in_use()) ? DECORATE_SHORT_REFS : 0;
>> +}
>
> FYI, I fixed this to
>
> static int auto_decoration_style(void)
>
> while queuing to make it compile.
No problem. Do I need to submit a second version of the patch with a
test for `git -p log`?
-Alex
2017-03-22 10:54 GMT-06:00 Junio C Hamano :
> Alex Henrie writes:
>> No problem. Do I need to submit a second version of the patch with a
>> test for `git -p log`?
>
> You do want to protect this "without an option, we default to
> 'auto'" feature f
2017-03-23 9:54 GMT-06:00 Junio C Hamano :
> Alex Henrie writes:
>
>> 2017-03-22 10:54 GMT-06:00 Junio C Hamano :
>>> Alex Henrie writes:
>>>> No problem. Do I need to submit a second version of the patch with a
>>>> test for `git -p log`?
>>&
2017-03-23 12:03 GMT-06:00 Junio C Hamano :
> Alex Henrie writes:
>
>> Yes, that makes sense. I assume that when you talk about 'next', you
>> mean 'master'?
>
> No, I do mean 'next'. See "A note from the maintainer" post tha
Signed-off-by: Alex Henrie
---
builtin/log.c | 9 -
t/t4202-log.sh | 10 +-
2 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/builtin/log.c b/builtin/log.c
index 281af8c1e..d755a5960 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -52,6 +52,11 @@ struct
Any news about this patch?
2017-03-21 22:24 GMT+01:00 Alex Hoffman :
> Hi, Brian,
>
> We definitely prefer the wrapper function oid_to_hex() to
> sha1_to_hex(). Thanks for feedback.
> Below is the updated patch:
>
> ---
> bisect.c | 6 +++---
> 1 file changed, 3
-- >8 --
>From 445d45027bb5b7823338cf111910d2884af6318b Mon Sep 17 00:00:00 2001
From: Alex Vandiver
Date: Tue, 3 Oct 2017 23:27:46 -0700
Subject: [PATCH] fsmonitor: Read entirety of watchman output
In perl, setting $/ sets the string that is used as the "record
separator," which sets the boundary that the
. But this also doesn't seem worthy of a new top-level command.
Do folks have feelings about surfacing this information, and where such
logic should live?
- Alex
this information from
repositories, with a standard git install. That directory only
contains developer tools, which aren't part of the install, no?
- Alex
ltered.
- Alex
Signed-off-by: Alex Vandiver
---
Documentation/git.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 1fca63634..720db196e 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -594,6 +594,10 @@ into it.
Unsetting the
This provides small performance savings.
Signed-off-by: Alex Vandiver
---
t/t7519/fsmonitor-watchman | 2 +-
templates/hooks--fsmonitor-watchman.sample | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/t/t7519/fsmonitor-watchman b/t/t7519/fsmonitor-watchman
tmap until after tweak_split_index
has been called to merge in the base index as well.
Signed-off-by: Alex Vandiver
---
cache.h | 1 +
fsmonitor.c | 38 --
read-cache.c | 4
3 files changed, 29 insertions(+), 14 deletions(-)
diff --git a/cache.h
Signed-off-by: Alex Vandiver
---
t/t7519/fsmonitor-watchman | 3 ++-
templates/hooks--fsmonitor-watchman.sample | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/t/t7519/fsmonitor-watchman b/t/t7519/fsmonitor-watchman
index a3e30bf54..377edc7be 100755
--- a
A few fixes found from playing around with the fsmonitor branch in
next.
- Alex
; - q[Doe, jane ],
> - q["Jane Doe ],
> - q['Jane 'Doe' ],
> - q[Jane@:;\.,()<>Doe ],
> - q[Jane Doe],
> - q[ Jane Doe]);
> -
> -my @known_failure_list = (q[Jane\ Doe ],
> - q["Doe, Ja"ne ],
> - q["Doe, Katarina" Jane ],
> - q[Jane j...@example.com],
> - q["Jane "Kat"a" ri"na" ",Doe" ],
> - q[Jane Doe],
> - q[Jane "Doe "],
> - q[\"Jane Doe ],
> - q[Jane\"\" Doe ],
> - q['Jane "Katarina\" \' Doe' ]);
> -
> -foreach my $str (@success_list) {
> - my @expected = map { $_->format } Mail::Address->parse("$str");
> - my @actual = Git::parse_mailboxes("$str");
> - is_deeply(\@expected, \@actual, qq[same output : $str]);
> -}
> -
> -TODO: {
> - local $TODO = "known breakage";
> - foreach my $str (@known_failure_list) {
> - my @expected = map { $_->format } Mail::Address->parse("$str");
> - my @actual = Git::parse_mailboxes("$str");
> - is_deeply(\@expected, \@actual, qq[same output : $str]);
> - }
> -}
> -
> -my $is_passing = eval { Test::More->is_passing };
> -exit($is_passing ? 0 : 1) unless $@ =~ /Can't locate object method/;
--
Alex Bennée
Matthieu Moy writes:
> From: Alex Bennée
>
> We had a regression that broke Linux's get_maintainer.pl. Using
> Mail::Address to parse email addresses fixed it, but let's protect
> against future regressions.
>
> Patch-edited-by: Matthieu Moy
> Signed-of
ncy,
> but it's easy enough to save the trouble of extra-dependency to the end
> user or packager.
>
> Signed-off-by: Matthieu Moy
Reviewed-by: Alex Bennée
> ---
> No change since v2.
>
> git-send-email.perl | 3 +-
> perl/Git/FromCPAN/Mail/Addre
Matthieu Moy writes:
> We now use Mail::Address unconditionaly, hence parse_mailboxes is now
> dead code. Remove it and its tests.
>
> Signed-off-by: Matthieu Moy
Reviewed-by: Alex Bennée
> ---
> No change since v2.
>
> p
The error message can be seen by running
`git config gc.reflogexpire foo` and then `git reflog expire`.
Signed-off-by: Alex Henrie
---
builtin/reflog.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/reflog.c b/builtin/reflog.c
index 7ed0e85..f96ca2a 100644
--- a
Signed-off-by: Alex Henrie
---
git-submodule.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-submodule.sh b/git-submodule.sh
index 36797c3..25b1ddf 100755
--- a/git-submodule.sh
+++ b/git-submodule.sh
@@ -904,7 +904,7 @@ Maybe you want to use 'update -
Signed-off-by: Alex Henrie
---
builtin/pack-objects.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/pack-objects.c b/builtin/pack-objects.c
index 62cc16d..1c63f8f 100644
--- a/builtin/pack-objects.c
+++ b/builtin/pack-objects.c
@@ -25,8 +25,8 @@
#include "
Signed-off-by: Alex Henrie
---
builtin/show-ref.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/show-ref.c b/builtin/show-ref.c
index dfbc314..d9c1633 100644
--- a/builtin/show-ref.c
+++ b/builtin/show-ref.c
@@ -8,7 +8,7 @@
static const char * const
-u and -i can only be given if -m, --reset, or --prefix is given.
Without parentheses, it looks like -u and -i can be used no matter
what, and the second pair of brackets is confusing.
Signed-off-by: Alex Henrie
---
builtin/read-tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Signed-off-by: Alex Henrie
---
builtin/show-ref.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/show-ref.c b/builtin/show-ref.c
index dfbc314..131ef28 100644
--- a/builtin/show-ref.c
+++ b/builtin/show-ref.c
@@ -8,7 +8,7 @@
static const char * const
<
git check-attr --stdin [-z] [-a | --all | ...] <
git hash-object --stdin-paths <
So if we need to say for clarity, we should also say
and for these other commands.
I think the most sane thing to do is to commit this patch as-is, and
then someone can submit a separate patch t
Hi,
This command is not working. Any advice?
Alex:testGit Alex$ git commit -a -m 'made a change'
On branch v1.0
Untracked files:
new_branch.txt
nothing added to commit but untracked files present
--
To unsubscribe from this list: send the line "unsubscribe git" in
the
1 - 100 of 266 matches
Mail list logo
