Am 11.11.2016 um 00:53 schrieb Junio C Hamano:
> Johannes Schindelin writes:
>
>> When making sure that background tasks are cleaned up in 5babb5b
>> (t6026-merge-attr: clean up background process at end of test case,
>> 2016-09-07), we considered to let the background task sleep longer, just
>>
This is the second time i am sending you this mail.I, Friedrich Mayrhofer
Donate $ 1,000,000.00 to You, Email Me personally for more details.
Regards.
Friedrich Mayrhofer
On Thu, Nov 10, 2016 at 9:36 AM, Karthik Nayak wrote:
> On Wed, Nov 9, 2016 at 4:57 AM, Jacob Keller wrote:
>> On Tue, Nov 8, 2016 at 12:11 PM, Karthik Nayak wrote:
>>> From: Karthik Nayak
>>>
>>> Add support for %(objectname:short=) which would print the
>>> abbreviated unique objectname of gi
On Thu, Nov 10, 2016 at 9:31 AM, Karthik Nayak wrote:
> On Wed, Nov 9, 2016 at 4:52 AM, Jacob Keller wrote:
>> On Tue, Nov 8, 2016 at 12:11 PM, Karthik Nayak wrote:
>>
>> Ok. How does this handle whitespace? The previous if implementation
>> treated whitespace as trimming to ignore. Does this re
On Thu, Nov 10, 2016 at 3:26 PM, Junio C Hamano wrote:
> Jacob Keller writes:
>
>>> @@ -49,6 +51,10 @@ static struct used_atom {
>>> enum { C_BARE, C_BODY, C_BODY_DEP, C_LINES, C_SIG,
>>> C_SUB } option;
>>> unsigned int nlines;
>>>
On Thu, Nov 10, 2016 at 04:13:28PM -0800, Jonathan Tan wrote:
> builtin/fetch.c redundantly calculates refmaps for tags twice. Remove
> the first calculation.
>
> This is only a code simplification and slight performance improvement -
> the result is unchanged, as the redundant refmaps are subseq
Junio C Hamano writes:
> Junio C Hamano writes:
>
>> I'll report back an updated schedule when able.
>
> I pushed some updates out on 'master' today. Between 'master' and
> 'pu' on the first-parent history there is a merge 52975d2b1f ("Merge
> branch 'ls/macos-update' into jch", 2016-11-10) and
builtin/fetch.c redundantly calculates refmaps for tags twice. Remove
the first calculation.
This is only a code simplification and slight performance improvement -
the result is unchanged, as the redundant refmaps are subsequently
removed by the invocation to "ref_remove_duplicates" anyway.
This
Johannes Schindelin writes:
> When making sure that background tasks are cleaned up in 5babb5b
> (t6026-merge-attr: clean up background process at end of test case,
> 2016-09-07), we considered to let the background task sleep longer, just
> to be certain that it will still be running when we wan
Karthik Nayak writes:
> else if (!strcmp(arg, "short"))
> - atom->u.objectname = O_SHORT;
> - else
> + atom->u.objectname.option = O_SHORT;
> + else if (skip_prefix(arg, "short=", &arg)) {
> + atom->u.objectname.option = O_LENGTH;
> +
Jacob Keller writes:
>> @@ -49,6 +51,10 @@ static struct used_atom {
>> enum { C_BARE, C_BODY, C_BODY_DEP, C_LINES, C_SIG,
>> C_SUB } option;
>> unsigned int nlines;
>> } contents;
>> + struct {
>> +
Karthik Nayak writes:
>> Minor nit. I'm not sure what standard we use here at Git, but
>> traditionally, I prefer to see { } blocks on all sections even if only
>> one of them needs it. (That is, only drop the braces when every
>> section is one line.) It also looks weird with a comment since it
Jacob Keller writes:
> Ok, so I have only one minor nit, but otherwise this looks quite good
> to me. A few comments explaining my understanding, but only one
> suggested
> change which is really a minor nit and not worth re-rolling just for it.
As you didn't snip parts you didn't comment, I'll
On Thu, Nov 10, 2016 at 02:07:30PM -0800, Junio C Hamano wrote:
> Kristoffer Haugsbakk writes:
>
> > Signed-off-by: Kristoffer Haugsbakk
> > ---
> > Documentation/gitcore-tutorial.txt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/gitcore-tutorial.
On Thu, Nov 10, 2016 at 02:55:06PM -0800, Junio C Hamano wrote:
> If we ensure that the process is still running, then such a check is
> a good belt-and-suspenders way to catch a breakage in the mechanism
> we choose to ensure it. So probably we can require that the kill in
> the "when finished"
Jeff King writes:
> I do think the test would be a lot more obvious if it confirmed at the
> end of the test that the process was still running, as opposed to
> relying on test_when_finished to check it.
I agree that "check that the process is still running" is a wrong
thing to do in the first p
On Thu, Nov 10, 2016 at 02:30:36PM -0800, Junio C Hamano wrote:
> As everybody knows there is no appropriate timeout value that is
> good for everybody. I wonder if we can replace the sleep 1 with
> something like
>
> ( while sleep 3600; do :; done ) &
>
> so that leaked fd will be kept e
Johannes Schindelin writes:
>> OK. sleep.pid is a reasonable easy-to-access side effect we can
>> observe to make sure that the sleep-one-second merge driver was
>> indeed invoked, which was missing from the earlier round.
>
> No, this is incorrect. The condition that we need to know applies is
Kristoffer Haugsbakk writes:
> Signed-off-by: Kristoffer Haugsbakk
> ---
> Documentation/gitcore-tutorial.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gitcore-tutorial.txt
> b/Documentation/gitcore-tutorial.txt
> index 4546fa0..9860517 100644
> ---
Hi all,
On Thu, 10 Nov 2016, Junio C Hamano wrote:
> Andreas Schwab writes:
>
> > Commit 5babb5bdb3 ("t6026-merge-attr: clean up background process at end
> > of test case") added a kill command to clean up after the test, but this
> > can fail if the sleep command exits before the cleanup is e
On Thu, Nov 10, 2016 at 01:49:52PM -0800, Junio C Hamano wrote:
> Yes, I recall the IIS one raised and discussed at least twice on the
> list in the past, and it sounded that we want some solution to that.
The patches had some issues. I suspect the population of people who want
to run a git serve
On Wed, 2016-10-26 at 19:07 -0400, Matt McCutchen wrote:
> Maybe we would never hit any of these problems in practice, but they
> give me a bad enough feeling that I'm planning to write my own tool
> that tracks the upstream commit ID in a file (like a submodule) and
> doesn't generate any extra co
Jeff King writes:
>> I however do not know what the universally available simplest dummy
>> HTTP server would be. There probably are better alternative than
>> Apache with distro-customized ways of configuration that we have to
>> adjust.
>>
>> A solution around HTTP::Server::Simple sounds at
Hi Lars,
On Wed, 9 Nov 2016, Lars Schneider wrote:
> On 05 Nov 2016, at 10:50, Johannes Schindelin
> wrote:
>
> > I finally got around to rebase the Windows-specific patches (which seem to
> > not make it upstream as fast as we get new ones) on top of upstream Git
> > v2.11.0-rc0, and to bundl
On Thu, Nov 10, 2016 at 01:33:29PM -0800, Junio C Hamano wrote:
> Jeff King writes:
>
> > IMHO, the value in the http tests is not testing the server side, but
> > the client side. Without being able to set up a dummy HTTP server, we do
> > not have any way to exercise the client side of git-ove
Junio C Hamano writes:
> I'll report back an updated schedule when able.
I pushed some updates out on 'master' today. Between 'master' and
'pu' on the first-parent history there is a merge 52975d2b1f ("Merge
branch 'ls/macos-update' into jch", 2016-11-10) and that matches
what I expect to be in
Lars Schneider writes:
>> I've followed what was available at the public-inbox archive, but it
>> is unclear what the conclusion was.
>>
>> For the first one your "how about" non-patch, to which Peff said
>> "that's simple and good", looked good to me as well, but is it
>> available as a final
Jeff King writes:
> IMHO, the value in the http tests is not testing the server side, but
> the client side. Without being able to set up a dummy HTTP server, we do
> not have any way to exercise the client side of git-over-http at all.
> And people on macOS _do_ use that. :)
Amen to that.
I ho
From: Nguyễn Thái Ngọc Duy
Full pattern must be quoted. So 'pat"t"ern attr' will give exactly
'pat"t"ern', not 'pattern'. Also clarify that leading whitespaces are
not part of the pattern and document comment syntax.
Signed-off-by: Nguyễn Thái Ngọc Duy
Signed-off-by: Junio C Hamano
Signed-off-
From: Junio C Hamano
When 82dce998 (attr: more matching optimizations from .gitignore,
2012-10-15) changed a pointer to a string "*pattern" into an
embedded "struct pattern" in struct match_attr, it forgot to update
the comment that describes the structure.
Signed-off-by: Junio C Hamano
Signed-
The prefix check is not related the check of pathspec magic; also there
is no code that is relevant after we'd break the loop on a match for
"prefix:". So move the check before the loop and shortcircuit the outer
loop.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
pathspec.c |
From: Junio C Hamano
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/attr.c b/attr.c
index 4ae7801..05db667 100644
--- a/attr.c
+++ b/attr.c
@@ -183,6 +183,12 @@ static const char *pa
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
Documentation/gitattributes.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
index 8a061af..5b31797 100644
--- a/Documentation/gitattributes.txt
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
contrib/completion/git-completion.bash | 1 +
1 file changed, 1 insertion(+)
diff --git a/contrib/completion/git-completion.bash
b/contrib/completion/git-completion.bash
index 21016bf..90eb772 100644
--- a/contrib/completion/git-co
`prefix_pathspec` is quite a lengthy function and we plan on adding more.
Split it up for better readability. As we want to add code into the
inner loop of the long magic parsing, we also benefit from lower
indentation.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
pathspec.c |
The new switch passes the pathspec to `git submodule update --init`
which is called after the actual clone is done.
Additionally this configures the submodule.defaultUpdatePath to
be the given pathspec, such that any future invocation of
`git submodule update --init-default-paths` will keep up
wit
The new switch `--init-default-path` initializes the submodules which are
configured in `submodule.defaultUpdatePath` instead of those given as
command line arguments before updating. In the first implementation this
is made incompatible with further command line arguments as it is
unclear what the
In our own .gitattributes file we have attributes such as:
*.[ch] whitespace=indent,trail,space
When querying for attributes we want to be able to ask for the exact
value, i.e.
git ls-files :(attr:whitespace=indent,trail,space)
should work, but the commas are used in the attr magic to i
From: Junio C Hamano
Often a potential caller has pair that
represents the path it wants to ask attributes for; when
path[pathlen] is not NUL, the caller has to xmemdupz()
only to call git_check_attr().
Add git_check_attr_counted() that takes such a counted
string instead of "const char *path".
It's not used outside the attr code, so let's keep it private.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c | 4 ++--
attr.h | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/attr.c b/attr.c
index 60d7eec..19a3651 100644
--- a/attr.c
+++ b/attr.c
@@
The pathspec mechanism is extended via the new
":(attr:eol=input)pattern/to/match" syntax to filter paths so that it
requires paths to not just match the given pattern but also have the
specified attrs attached for them to be chosen.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
Instead of having a global attr stack, attach the stack to each check.
This allows to use the attr in a multithreaded way.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c| 101 +++---
attr.h| 4 ++-
hashmap.
From: Junio C Hamano
Since nobody uses the old API, make it file-scope static, and update
the documentation to describe the new API.
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
Documentation/technical/api-gitattributes.txt | 82 +++
From: Junio C Hamano
It holds an interned string, and git_attr_name() is a way to peek
into it. Make sure the involved pointer types are pointer-to-const.
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c | 2 +-
attr.h | 4 ++--
2 files cha
From: Junio C Hamano
Export attr_name_valid() function, and a helper function that
returns the message to be given when a given pair
is not a good name for an attribute.
We could later update the message to exactly spell out what the
rules for a good attribute name are, etc.
Signed-off-by: Jun
From: Junio C Hamano
The double-loop wants to do an early return immediately when one
matching macro is found. Eliminate the extra variable 'a' used for
that purpose and rewrite the "assign the found item to 'a' to make
it non-NULL and force the loop(s) to terminate" with a direct return
from th
From: Junio C Hamano
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
commit.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/commit.c b/commit.c
index 856fd4a..41b2fdd 100644
--- a/commit.c
+++ b/commit.c
@@ -415,8 +415,7 @@
This revamps the API of the attr subsystem to be thread safe.
Before we had the question and its results in one struct type.
The typical usage of the API was
static struct git_attr_check *check;
if (!check)
check = git_attr_check_initl("text", NULL);
git_check_attr(path, chec
From: Junio C Hamano
This function used to be called with check=NULL to signal it to
collect all attributes in the global check_all_attr[] array.
Because the longer term plan is to allocate check_all_attr[] and
attr_stack data structures per git_attr_check instance (i.e. "check"
here) to make th
From: Junio C Hamano
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c | 40 +++-
1 file changed, 39 insertions(+), 1 deletion(-)
diff --git a/attr.c b/attr.c
index 246a5d0..60d7eec 100644
--- a/attr.c
+++
From: Junio C Hamano
The collect_some_attrs() function has an ugly hack since
06a604e6 (attr: avoid heavy work when we know the specified attr is
not defined, 2014-12-28) added an optimization that relies on the
fact that the caller knows what attributes it is interested in, so
that we can leave
From: Junio C Hamano
The callchain that starts from git_check_attrs() down to
collect_some_attrs() used to take an array of git_attr_check_elem
as their parameters. Pass the enclosing git_attr_check instance
instead, so that they will have access to new fields we will add to
the data structure.
From: Junio C Hamano
The remaining callers are all simple "I have N attributes I am
interested in. I'll ask about them with various paths one by one".
After this step, no caller to git_check_attrs() remains. After
removing it, we can extend "struct git_attr_check" struct with data
that can be
From: Junio C Hamano
One codepath needs to just empty the git_attr_check_elem array in
the git_attr_check structure, without releasing the entire resource.
Introduce a helper to do so and rewrite git_attr_check_clear() using
it.
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed
From: Junio C Hamano
This updates the other two ways the attribute check is done via an
array of "struct git_attr_check_elem" elements. These two niches
appear only in "git check-attr".
* The caller does not know offhand what attributes it wants to ask
about and cannot use git_attr_check_in
From: Junio C Hamano
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/attr.c b/attr.c
index a7f2c3f..95416d3 100644
--- a/attr.c
+++ b/attr.c
@@ -469,7 +469,7 @@ static void
From: Junio C Hamano
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/attr.c b/attr.c
index 05db667..a7f2c3f 100644
--- a/attr.c
+++ b/attr.c
@@ -300,7 +300,7 @@ static struc
From: Junio C Hamano
There are too many repetitious "I have this new attr_stack element;
push it at the top of the stack" sequence. The new helper function
push_stack() gives us a way to express what is going on at these
places, and as a side effect, halves the number of times we mention
the att
From: Junio C Hamano
A common pattern to check N attributes for many paths is to
(1) prepare an array A of N git_attr_check_elem items;
(2) call git_attr() to intern the N attribute names and fill A;
(3) repeatedly call git_check_attrs() for path with N and A;
A look-up for these N attribute
From: Junio C Hamano
Throughout this series, we are trying to use "check" to name an
instance of "git_attr_check" structure; let's rename a "check" that
refers to an array whose elements are git_attr_check_elem to avoid
confusion.
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Sign
From: Junio C Hamano
Signed-off-by: Junio C Hamano
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
attr.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/attr.c b/attr.c
index eec5d7d..45aec1b 100644
--- a/attr.c
+++ b/attr.c
@@ -402,8 +402,8 @@ static s
previous discussion:
https://public-inbox.org/git/20161028185502.8789-1-sbel...@google.com/
Changes since v2:
* dropped one patch (that exposes git_attr_counted, nobody uses
it throughout the series )
* added pathspec guarding and added a test with git-add to see if it works.
* squashed "SQUASH
From: Junio C Hamano
The traditional API to check attributes is to prepare an N-element
array of "struct git_attr_check" and pass N and the array to the
function "git_check_attr()" as arguments.
In preparation to revamp the API to pass a single structure, in
which these N elements are held, rena
From: Junio C Hamano
If any error is noticed after the match_attr structure is allocated,
we shouldn't just return NULL from this function.
Add a fail_return label that frees the allocated structure and
returns NULL, and consistently jump there when we want to return
NULL after cleaning up.
Sig
Andreas Schwab writes:
> Commit 5babb5bdb3 ("t6026-merge-attr: clean up background process at end
> of test case") added a kill command to clean up after the test, but this
> can fail if the sleep command exits before the cleanup is executed.
> Ignore the error from the kill command.
>
> Explicit
Duy Nguyen writes:
> On Thu, Nov 10, 2016 at 6:09 PM, Duy Nguyen wrote:
>> On Thu, Nov 10, 2016 at 3:12 AM, Junio C Hamano wrote:
>>> Nguyễn Thái Ngọc Duy writes:
>>>
---
v2 changes just the subject line
>>>
>>> That's not sufficient, is it? What you did in the documentation
>>> w
On Wed, Nov 9, 2016 at 5:01 AM, Jacob Keller wrote:
> On Tue, Nov 8, 2016 at 12:11 PM, Karthik Nayak wrote:
>
>>
>> - if (starts_with(name, "refname"))
>> + if (starts_with(name, "refname")) {
>> refname = ref->refname;
>> - else i
On Wed, Nov 9, 2016 at 4:52 AM, Jacob Keller wrote:
> On Tue, Nov 8, 2016 at 12:11 PM, Karthik Nayak wrote:
>
> Ok. How does this handle whitespace? The previous if implementation
> treated whitespace as trimming to ignore. Does this require an exact
> whitespace match? It appears by the code tha
On Wed, Nov 9, 2016 at 4:57 AM, Jacob Keller wrote:
> On Tue, Nov 8, 2016 at 12:11 PM, Karthik Nayak wrote:
>> From: Karthik Nayak
>>
>> Add support for %(objectname:short=) which would print the
>> abbreviated unique objectname of given length. When no length is
>> specified, the length is 'DEF
>>
>> /*
>> @@ -370,7 +368,7 @@ static void align_atom_handler(struct atom_value *atomv,
>> struct ref_formatting_s
>> push_stack_element(&state->stack);
>> new = state->stack;
>> new->at_end = end_align_handler;
>> - new->at_end_data = &atomv->u.align;
>> + ne
Hey,
On Wed, Nov 9, 2016 at 4:43 AM, Jacob Keller wrote:
> On Tue, Nov 8, 2016 at 12:11 PM, Karthik Nayak wrote:
>> From: Karthik Nayak
>>
>> +Some atoms like %(align) and %(if) always require a matching %(end).
>> +We call them "opening atoms" and sometimes denote them as %($open).
>> +
>> +Wh
On Thu, Nov 10, 2016 at 12:07:14PM +0100, Lars Schneider wrote:
> > Using Apache in the tests has been the source of frequent portability
> > problems and configuration headaches. I do wonder if we'd be better off
> > using some small special-purpose web server (even a short perl script
> > writte
On Thu, Nov 10, 2016 at 01:10:17PM +0100, Matthieu Moy wrote:
> Lars Schneider writes:
>
> > I haven't looked at an implemenation approach at all. I wonder if this could
> > be OK from a conceptional point of view or if there are obvious security
> > problems that I am missing.
>
> Did you con
Lars Schneider writes:
> I haven't looked at an implemenation approach at all. I wonder if this could
> be OK from a conceptional point of view or if there are obvious security
> problems that I am missing.
Did you consider just running "git credential" from the filter? It may
not be the perfec
Hi,
we just implemented the first "real-world" user of the new clean/smudge
"filter protocol" interface (see "convert: add filter..process option"
edcc858 for details) and the results are fantastic. Filtering 12,000 files in
my artificial test repo is more than 60x faster (depending on the platfo
On Thu, Nov 10, 2016 at 6:09 PM, Duy Nguyen wrote:
> On Thu, Nov 10, 2016 at 3:12 AM, Junio C Hamano wrote:
>> Nguyễn Thái Ngọc Duy writes:
>>
>>> ---
>>> v2 changes just the subject line
>>
>> That's not sufficient, is it? What you did in the documentation
>> would raise the same "Hmph, is t
> On 10 Nov 2016, at 00:39, Junio C Hamano wrote:
>
> larsxschnei...@gmail.com writes:
>
>> From: Lars Schneider
>>
>> Apple removed the OpenSSL header files in macOS and therefore Git does
>> not build out of the box on macOS anymore. See previous discussion with
>> Torsten here: http://publ
From: Lars Schneider
Apple removed the OpenSSL header files in macOS 10.11 and above. OpenSSL
was deprecated since macOS 10.7.
Set `NO_OPENSSL` and `APPLE_COMMON_CRYPTO` to `YesPlease` as default for
macOS. It is possible to override this and use OpenSSL by defining
`NO_APPLE_COMMON_CRYPTO`.
Si
On Thu, Nov 10, 2016 at 3:12 AM, Junio C Hamano wrote:
> Nguyễn Thái Ngọc Duy writes:
>
>> ---
>> v2 changes just the subject line
>
> That's not sufficient, is it? What you did in the documentation
> would raise the same "Hmph, is this only about HEAD?" and unlike the
> commit subject, it wil
> On 07 Nov 2016, at 22:20, Jeff King wrote:
>
> On Sun, Nov 06, 2016 at 10:42:36PM +0100, Lars Schneider wrote:
>
>>> From: Lars Schneider
>>>
>>> TravisCI changed their default macOS image from 10.10 to 10.11 [1].
>>> Unfortunately the HTTPD tests do not run out of the box using the
>>> pre
On Thu, Nov 10, 2016 at 7:23 AM, Jeff King wrote:
> On Wed, Nov 09, 2016 at 04:18:29PM -0800, Junio C Hamano wrote:
>
>> Jeff King writes:
>>
>> > On Wed, Nov 09, 2016 at 02:58:37PM -0800, Junio C Hamano wrote:
>> >
>> > I'm slightly confused. Did you mean "supporting any in-tree symlink to
>> >
We currently have openings to fund early startups at the preferential interest
rate of two percent per year.
Regards,
Larry Koetze
On Wed, Nov 9, 2016 at 1:23 PM, Roman Terekhov wrote:
> Hi,
>
> I want to ask about git clean -dXf command behaviour.
>
> I do the following:
>
> $ mkdir gitignore_test
> $ cd gitignore_test/
> $ git init
> Initialized empty Git repository in ~/gitignore_test/.git/
>
> $ echo *.sln > .gitignore
>
Commit 5babb5bdb3 ("t6026-merge-attr: clean up background process at end
of test case") added a kill command to clean up after the test, but this
can fail if the sleep command exits before the cleanup is executed.
Ignore the error from the kill command.
Explicitly check for the existence of the pi
Am 05.11.2016 um 10:50 schrieb Johannes Schindelin:
> Dear Git users,
>
> I finally got around to rebase the Windows-specific patches (which seem to
> not make it upstream as fast as we get new ones) on top of upstream Git
> v2.11.0-rc0, and to bundle installers, portable Git and MinGit [*1*]:
>
85 matches
Mail list logo
