Stefan Beller writes:
> +static void pp_buffer_stderr(struct parallel_processes *pp)
> +{
> + int i;
> +
> + while ((i = poll(pp->pfd, pp->max_processes, 100)) < 0) {
> + if (errno == EINTR)
> + continue;
> + pp_cleanup(pp);
> + die_
Stefan Beller writes:
> run-command.c | 264
> +
> run-command.h | 36 +++
> t/t0061-run-command.sh | 20
> test-run-command.c | 24 +
> 4 files changed, 344 insertions(+)
I think we are almost there, but the
On Tue, Sep 22, 2015 at 05:14:42PM -0700, Stefan Beller wrote:
> We should not care if the call to poll failed, as we're in an infinite loop
> and
> can only get out with the correct read(..). So maybe an implementation like
> this
> would already suffice:
>
> ssize_t xread(int fd, void *buf, s
In a later patch we enable parallel processing of submodules, this
only adds the possibility for it. So this change should not change
any user facing behavior.
Signed-off-by: Stefan Beller
---
submodule.c | 119 +++-
1 file changed, 85 inse
Split the fetching part out to its own function,
this allow us in a later patch to convert cmd_update in C.
Signed-off-by: Stefan Beller
---
git-submodule.sh | 164 ---
1 file changed, 84 insertions(+), 80 deletions(-)
diff --git a/git-submodu
We will need computing the return value in a later patch without the
wait.
Signed-off-by: Stefan Beller
---
run-command.c | 56 ++--
1 file changed, 34 insertions(+), 22 deletions(-)
diff --git a/run-command.c b/run-command.c
index 28e1d55..2b
We need the submodule update strategies in a later patch.
Signed-off-by: Stefan Beller
---
submodule-config.c | 11 +++
submodule-config.h | 1 +
2 files changed, 12 insertions(+)
diff --git a/submodule-config.c b/submodule-config.c
index afe0ea8..8b8c7d1 100644
--- a/submodule-config.
Split the recursion part out to its own function, this allow us
in a later patch to convert cmd_update in C.
Signed-off-by: Stefan Beller
---
git-submodule.sh | 47 ++-
1 file changed, 26 insertions(+), 21 deletions(-)
diff --git a/git-submodule.sh b/
This will make parallelisation easier in a followup patch. This is just
a translation from shell to C, hopefully not introducing any bugs.
Signed-off-by: Stefan Beller
---
builtin/submodule--helper.c | 251
git-submodule.sh| 135 +-
This allows to run external commands in parallel with ordered output
on stderr.
If we run external commands in parallel we cannot pipe the output directly
to the our stdout/err as it would mix up. So each process's output will
flow through a pipe, which we buffer. One subprocess can be directly
pi
CC: Eric Sunshine
Signed-off-by: Stefan Beller
---
submodule-config.c | 74 +-
1 file changed, 29 insertions(+), 45 deletions(-)
diff --git a/submodule-config.c b/submodule-config.c
index 393de53..afe0ea8 100644
--- a/submodule-config.c
+++ b/
>From the man page:
EAGAIN The file descriptor fd refers to a file other than a socket
and has been marked nonblocking (O_NONBLOCK), and the read
would block.
EAGAIN or EWOULDBLOCK
The file descriptor fd refers to a socket and has been marked
nonblocking (O_NONBLOCK), a
This enables the work of the previous patches.
Signed-off-by: Stefan Beller
---
Documentation/fetch-options.txt | 7 +++
builtin/fetch.c | 6 +-
builtin/pull.c | 6 ++
submodule.c | 3 +--
submodule.h | 2 +
Split the cloning part out to its own function,
this allow us in a later patch to convert cmd_update in C.
Signed-off-by: Stefan Beller
---
git-submodule.sh | 31 ---
1 file changed, 20 insertions(+), 11 deletions(-)
diff --git a/git-submodule.sh b/git-submodule.sh
i
The new call will read from a file descriptor into a strbuf once. The
underlying call xread_nonblock is meant to execute without blocking if
the file descriptor is set to O_NONBLOCK. It is a bug to call
strbuf_read_once on a file descriptor which would block.
Signed-off-by: Stefan Beller
---
str
From: Jonathan Nieder
The "Pushing submodule " progress output correctly goes to
stderr, but "Fetching submodule " is going to stdout by mistake.
Fix it to write to stderr.
Noticed while trying to implement a parallel submodule fetch. When
this particular output line went to a different file de
Provide a wrapper to read(), similar to xread(), that restarts on
EINTR but not EAGAIN (or EWOULDBLOCK). This enables the caller to
handle polling itself, possibly polling multiple sockets or performing
some other action.
Helped-by: Jacob Keller
Helped-by: Jeff King ,
Helped-by: Junio C Hamano
S
Today there was lots of discussion on the correct way of reading the
strbufs as well as some discussion on the structure of the
asynchronous parallel process loop.
Patches 1-8 bring parallel fetching of submodules, and have had some good
exposure
to review and feedback is incorporated.
Patches 9
Stefan Beller writes:
> We should not care if the call to poll failed, as we're in an infinite loop
> and
> can only get out with the correct read(..).
I think I agree with that reasoning. The only thing we want out of
this call to poll(2) is to delay calling read(2) again when we know
we woul
Eric Wong wrote:
> Victor Leschuk wrote:
> > The thing is that git-cat-file keeps growing during work when running
> > in "batch" mode. See the figure attached: it is for cloning a rather
> > small repo (1 hour to clone about ~14000 revisions). However the clone
> > of a large repo (~28 revis
On Tue, Sep 22, 2015 at 1:00 PM, Junio C Hamano wrote:
> Jeff King writes:
>
>> On Tue, Sep 22, 2015 at 12:45:51PM -0700, Junio C Hamano wrote:
>>
>>> One caveat is that the caller may not know in the first place.
>>>
>>> The last time I checked the existing callers of xread(), there were
>>> a f
Victor Leschuk wrote:
> The thing is that git-cat-file keeps growing during work when running
> in "batch" mode. See the figure attached: it is for cloning a rather
> small repo (1 hour to clone about ~14000 revisions). However the clone
> of a large repo (~28 revisions) took about 2 weeks and
Hi,
I noticed that t5561 fails on my machine when compiling with
"make PROFILE=GEN". Luckily, the reason seems to be the test only,
not the tool it is testing.
I tracked it down that far that log_div() (defined in
t/t5561-http-backend.sh but used in t/t556x_common) appends
the given text to the a
Stefan Beller writes:
> On Tue, Sep 22, 2015 at 2:41 PM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> On Tue, Sep 22, 2015 at 12:53 PM, Junio C Hamano wrote:
Stefan Beller writes:
> So how would you find out when we are done?
while (1) {
From: Jacob Keller
expand_notes_ref is used by --ref from git-notes(1) and --notes from the
git log to find the full refname of a notes reference. Previously the
documentation of these options was not clear about what sorts of
expansions would be performed. Fix the documentation to clearly and
ac
larsxschnei...@gmail.com writes:
> From: Lars Schneider
>
> diff to v6:
> * fix spaces in .gitattributes for Git-LFS files (old "[:space:]", new
> "[[:space:]]")
> * generated patch on top of next (95c4325) to resolve merge conflicts
>
> I am sorry about the "[:space:]" bug this late. I had the
On Tue, Sep 22, 2015 at 2:41 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> On Tue, Sep 22, 2015 at 12:53 PM, Junio C Hamano wrote:
>>> Stefan Beller writes:
>>>
So how would you find out when we are done?
>>>
>>> while (1) {
>>> if (we have available slot)
larsxschnei...@gmail.com writes:
> From: Lars Schneider
>
> The functions “gitConfig” and “gitConfigBool” are almost identical. Make
> “gitConfig” more generic by adding an optional type specifier. Use the type
> specifier “—bool” with “gitConfig” to implement “gitConfigBool. This prepares
> t
Stefan Beller writes:
> On Tue, Sep 22, 2015 at 12:53 PM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> So how would you find out when we are done?
>>
>> while (1) {
>> if (we have available slot)
>> ask to start a new one;
>>
Remi Pommarel writes:
> I have one last question thought. Wouldn't it be nice if we had
> configure to autodetect the need for -lssl with libcurl?
Sure. I do not think anybody tried, but it would be nice.
> We could make
> configure to check for Curl_ssl_init function symbol in libcurl,
> whic
On Tue, Sep 22, 2015 at 12:53 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> So how would you find out when we are done?
>
> while (1) {
> if (we have available slot)
> ask to start a new one;
> if (nobody is running anymore)
"Keller, Jacob E" writes:
> On Tue, 2015-09-22 at 13:40 -0700, Junio C Hamano wrote:
>> How about phrasing it totally differently?
>>
>> The ref specifies the full refname when it begins with
>> `refs/notes/`; otherwise `ref/notes/` is prefixed to form a
>> full name of the ref.
>
On Tue, 2015-09-22 at 13:40 -0700, Junio C Hamano wrote:
> How about phrasing it totally differently?
>
> The ref specifies the full refname when it begins with
> `refs/notes/`; otherwise `ref/notes/` is prefixed to form a
> full name of the ref.
>
> I think that would remove th
On Tue, 2015-09-22 at 13:40 -0700, Junio C Hamano wrote:
> Jacob Keller writes:
>
> > From: Jacob Keller
> >
> > The --notes and --ref parameter for selecting which notes ref to
> > operate
> > on are based off of expand_notes_ref functionality. The
> > documentation
> > mentioned that an unqua
On Tue, 2015-09-22 at 22:00 +0200, Johannes Schindelin wrote:
> Hi Joakim,
>
> On 2015-09-21 19:08, Joakim Tjernlund wrote:
> > On Mon, 2015-09-21 at 09:48 -0700, Junio C Hamano wrote:
> > > Duy Nguyen writes:
> > >
> > > > Is it really necessary to remove write access in $GIT_DIR? Do we (git
>
Theodore Ts'o writes:
> On Tue, Sep 22, 2015 at 04:11:23PM -0400, Josh Boyer wrote:
>> Oh, context would help, yes. In the case of the tree I'm parsing, I
>> know for a fact that the commit history is entirely linear and will
>> (should) always remain so. E.g.
>>
>> A - B - C - D - E - F ... {
On Tue, Sep 22, 2015 at 04:11:23PM -0400, Josh Boyer wrote:
> Oh, context would help, yes. In the case of the tree I'm parsing, I
> know for a fact that the commit history is entirely linear and will
> (should) always remain so. E.g.
>
> A - B - C - D - E - F ... {N}
>
> So yes, finding e.g. th
Jacob Keller writes:
> From: Jacob Keller
>
> The --notes and --ref parameter for selecting which notes ref to operate
> on are based off of expand_notes_ref functionality. The documentation
> mentioned that an unqualified ref argument would be taken as under
> `refs/notes/`. However, this does
On Mon, Sep 21, 2015 at 10:09:52AM -0700, Junio C Hamano wrote:
> I think I said this already, but I found these bits from your patch
>
> - $(LIBS) $(CURL_LIBCURL) $(EXPAT_LIBEXPAT)
> + $(CURL_LIBCURL) $(EXPAT_LIBEXPAT) $(LIBS)
>
> that first uses libcurl and then libs (wh
From: Jacob Keller
The --notes and --ref parameter for selecting which notes ref to operate
on are based off of expand_notes_ref functionality. The documentation
mentioned that an unqualified ref argument would be taken as under
`refs/notes/`. However, this does not clearly indicate that
`refs/he
On Tue, Sep 22, 2015 at 3:55 PM, Junio C Hamano wrote:
> Josh Boyer writes:
>
>> On Tue, Sep 22, 2015 at 2:40 PM, Konstantin Khomoutov
>> ...
>>> Hence, given any particular commit, you're able to trace all of its
>>> ancestry, but the reverse is not possible.
>>
>> That makes sense. I suppose I
Hi Joakim,
On 2015-09-21 19:08, Joakim Tjernlund wrote:
> On Mon, 2015-09-21 at 09:48 -0700, Junio C Hamano wrote:
>> Duy Nguyen writes:
>>
>> > Is it really necessary to remove write access in $GIT_DIR? Do we (git
>> > devs) have some guidelines about things in $GIT_DIR?
>>
>> Those who are allo
Jeff King writes:
> On Tue, Sep 22, 2015 at 12:45:51PM -0700, Junio C Hamano wrote:
>
>> One caveat is that the caller may not know in the first place.
>>
>> The last time I checked the existing callers of xread(), there were
>> a few that read from a file descriptor they did not open themselves
Josh Boyer writes:
> On Tue, Sep 22, 2015 at 2:40 PM, Konstantin Khomoutov
> ...
>> Hence, given any particular commit, you're able to trace all of its
>> ancestry, but the reverse is not possible.
>
> That makes sense. I suppose I will have to resort to parsing output
> of git-rev-list or somet
Stefan Beller writes:
> So how would you find out when we are done?
while (1) {
if (we have available slot)
ask to start a new one;
if (nobody is running anymore)
break;
collect the output fro
On Tue, Sep 22, 2015 at 12:45:51PM -0700, Junio C Hamano wrote:
> Jacob Keller writes:
>
> > I don't think this patch actually changes behavior as it stands now. I
> > think Junio's suggestion does. Personally, I'd prefer some sort of
> > warning when you use xread and get EAGAIN or EWOULDBLOCK.
Jacob Keller writes:
> I don't think this patch actually changes behavior as it stands now. I
> think Junio's suggestion does. Personally, I'd prefer some sort of
> warning when you use xread and get EAGAIN or EWOULDBLOCK. I'd rather
> see it somehow warn so that we can find the bug (since we rea
Michael Rappazzo writes:
>
> +--porcelain::
> + With `list`, output in an easy-to-parse format for scripts.
> + This format will remain stable across Git versions and regardless of
> user
> + configuration.
... and exactly what does it output? That would be the first
question a r
From: LDVSOFT
gitrepository-layout.txt: In description of `info' directory,
note about `$GIT_COMMON_DIR' was referencing `index'
instead of `info'.
Signed-off-by: LDVSOFT
---
Documentation/gitrepository-layout.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Docu
Yup, this was privately reported and I just squashed a fix in right now ;-)
Thanks. "cd t && make test-lint" would have caught it.
On Tue, Sep 22, 2015 at 12:11 PM, Michael Blume wrote:
> I'm seeing test failures
>
> non-executable tests: t9825-git-p4-handle-utf16-without-bom.sh
>
> ls -l shows
I'm seeing test failures
non-executable tests: t9825-git-p4-handle-utf16-without-bom.sh
ls -l shows that all the other tests are executable but t9825 isn't.
On Tue, Sep 22, 2015 at 9:02 AM, Junio C Hamano wrote:
> Lars Schneider writes:
>
>> This works.
>
> OK, and thanks; as I don't do perfor
On Tue, Sep 22, 2015 at 2:40 PM, Konstantin Khomoutov
wrote:
> On Tue, 22 Sep 2015 14:32:19 -0400
> Josh Boyer wrote:
>
>> Please CC me as I'm not subscribed.
>>
>> I was hoping someone could help me with the revision shorthand to get
>> the commit sha of a commit N commits after the initial comm
On Tue, Sep 22, 2015 at 11:37 AM, Junio C Hamano wrote:
> Jacob Keller writes:
>
>> The other issue here is that expand_notes_ref is called on the --ref
>> argument waaay before the current code even decides if the operation
>> is "read" or "write". Thus we'd have to break this out and handle
>>
I found a specific case in which git-svn improperly aborts:
1. I created a git-svn repository, named "git-svn repo", by cloned an
svn repository via the git-svn tool.
2. I created a normal git repository, named "configuration repo". I
renamed the master branch to "configuration". The initial commi
On Sat, Sep 12, 2015 at 12:37:33PM +0200, Julian Andres Klode wrote:
> Introduce an option to deny unsigned tags from entering
> a repository. This is useful in teams where members forget
> to sign their release tags.
>
> It does not actually check whether the signature is actually
> complete or v
On Tue, Sep 22, 2015 at 11:21 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> On Tue, Sep 22, 2015 at 8:58 AM, Junio C Hamano wrote:
>>> Eric Sunshine writes:
>>>
> while (1) {
> nr = read(fd, buf, len);
> - if ((nr < 0) && (errno == EAGA
On Tue, 22 Sep 2015 14:32:19 -0400
Josh Boyer wrote:
> Please CC me as I'm not subscribed.
>
> I was hoping someone could help me with the revision shorthand to get
> the commit sha of a commit N commits after the initial commit.
What happens if right after the initial commit, there have been f
On 22.09.15 08:23, Jacob Keller wrote:
> On Mon, Sep 21, 2015 at 9:55 PM, Torsten Bögershausen wrote:
>> But in any case I suggest to xread() as it is, and not to change the
>> functionality
>> behind the back of the users.
>>
>>
>
> I don't think this patch actually changes behavior as it stand
Jacob Keller writes:
> The other issue here is that expand_notes_ref is called on the --ref
> argument waaay before the current code even decides if the operation
> is "read" or "write". Thus we'd have to break this out and handle
> things very differently.
I think you hit the right nail here.
Hi All,
Please CC me as I'm not subscribed.
I was hoping someone could help me with the revision shorthand to get
the commit sha of a commit N commits after the initial commit. Thus
far I've figured out that to get the initial commit in a repository,
you can use:
git rev-list --max-parents=0 HE
On Mon, Sep 21, 2015 at 6:08 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> +void default_start_failure(void *data,
>> +struct child_process *cp,
>> +struct strbuf *err)
>> +{
>> + int i;
>> + struct strbuf sb = STRBUF_INIT;
>> +
>>
Stefan Beller writes:
> On Tue, Sep 22, 2015 at 8:58 AM, Junio C Hamano wrote:
>> Eric Sunshine writes:
>>
while (1) {
nr = read(fd, buf, len);
- if ((nr < 0) && (errno == EAGAIN || errno == EINTR))
- continue;
Michael Rappazzo writes:
> +/**
> + * get the main worktree
> + */
> +static struct worktree *get_main_worktree()
static struct worktree *get_main_worktree(void)
> +{
> + struct worktree *worktree = NULL;
> struct strbuf path = STRBUF_INIT;
> + struct strbuf worktree_path = STRBUF
On Tue, Sep 22, 2015 at 7:17 AM, Junio C Hamano wrote:
> Calls expand_notes_ref() made on a command line argument that
> specifies the source (which I think is similar to what the other
> recent topic calls "read-only") should be made to calls to a more
> lenient version (and you can start with ge
Michael Rappazzo writes:
> Refactoring will help transition this code to provide additional useful
> worktree functions.
>
> Signed-off-by: Michael Rappazzo
> ---
> worktree.c | 86
> ++
> 1 file changed, 64 insertions(+), 22 deletion
On Tue, Sep 22, 2015 at 8:58 AM, Junio C Hamano wrote:
> Eric Sunshine writes:
>
>>> while (1) {
>>> nr = read(fd, buf, len);
>>> - if ((nr < 0) && (errno == EAGAIN || errno == EINTR))
>>> - continue;
>>> + if (nr < 0) {
>>
Michael Rappazzo writes:
> worktree.c contains functions to work with and get information from
> worktrees. This introduction moves functions related to worktrees
> from branch.c into worktree.c
>
> Signed-off-by: Michael Rappazzo
> ---
> Makefile| 1 +
> branch.c| 79 +---
Stefan Beller writes:
> In a later patch we enable parallel processing of submodules, this
> only adds the possibility for it. So this change should not change
> any user facing behavior.
>
> Signed-off-by: Stefan Beller
> ---
> builtin/fetch.c | 3 +-
> submodule.c | 119
> +
Lars Schneider writes:
> If it is no extra work for you, you can remove the quotes around
> “db”. I can also create a new patch roll including the sed change
> and the quote change if it is easier for you.
Now you've tested the SQUASH??? for me, I can just squash that into
your original without
Gabor Bernat writes:
> On Mon, Sep 21, 2015 at 11:24 PM, Gábor Bernát
> ...
>> Agreed, :) did not abandoned this, just got caught up with many stuff.
>> Thanks for the help,
>
> So do I need to do anything else with this? :)
If you can fetch from me to see if the output from
git log -p orig
Lars Schneider writes:
> This works.
OK, and thanks; as I don't do perforce, the squash was without any
testing.
> Do we need the “-e” option?
In syntactic sense, no, but our codebase tends to prefer to have
one, because it is easier to spot which ones are the instructions if
you consistently
On Tue, Sep 22, 2015 at 02:12:59AM -0700, Victor Leschuk wrote:
> I've been playing with git-svn for some time already and as it seems
> to me there are two most important problems which make it hard to use
> in production for large repositories. Very low speed and large memory
> footprint of sync
Eric Sunshine writes:
>> while (1) {
>> nr = read(fd, buf, len);
>> - if ((nr < 0) && (errno == EAGAIN || errno == EINTR))
>> - continue;
>> + if (nr < 0) {
>> + if (errno == EINTR)
>> +
Jacob Keller writes:
> On Mon, Sep 21, 2015 at 3:39 PM, Stefan Beller wrote:
>
> Maybe change the title to "without blocking" instead of "nonblockingly"?
Both suggestions make sense ;-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.
On Mon, Sep 21, 2015 at 11:24 PM, Gábor Bernát
wrote:
> On Mon, Sep 21, 2015 at 11:22 PM, Eric Sunshine
> wrote:
>>
>> On Mon, Sep 21, 2015 at 3:52 PM, Junio C Hamano wrote:
>> > Eric Sunshine writes:
>> >> On Tue, Sep 8, 2015 at 1:32 PM, Junio C Hamano
>> >> wrote:
>> >>> Eric Sunshine write
On Mon, Sep 21, 2015 at 5:56 PM, Eric Sunshine wrote:
> On Mon, Sep 21, 2015 at 6:39 PM, Stefan Beller wrote:
>> We need the submodule update strategies in a later patch.
>>
>> Signed-off-by: Stefan Beller
>> ---
>> diff --git a/submodule-config.c b/submodule-config.c
>> @@ -326,6 +327,21 @@ sta
On Tue, Sep 22, 2015 at 7:17 AM, Junio C Hamano wrote:
> The current code before your patch limits the allowed pair of notes
> trees by insisting that both appear as the tips of refs somewhere in
> refs/notes/*. For allowing to merge from outside refs/notes/, you
> need to loosen the location the
Jacob Keller writes:
> I never got any better suggestion on how to allow the behavior
> desired, which is to enable merging from a non-notes location, in
> order to provide a standard location for remote notes, ie:
> refs/remote-notes//
Step back a bit and think again. I think you are blinded b
Victor Leschuk writes:
> We already do have some of these: 'no-metadata', 'no-checkout',
> no-auth-cache'. So I was just following the existing convention. Do
> you think we need to change it and stick with
> --catch-file-batch=1/--cat-file-batch=0 ?
Inventing a new --cat-file-batch=[0|1] is not
As for your remark regarding the option naming:
> An option whose name begins with no- looks somewhat strange. You
can even say --no-no-cat-file-batch from the command line, I
suspect.
We already do have some of these: 'no-metadata', 'no-checkout',
'no-auth-cache'. So I was just following the
Thanks Ray,
Ray Chen gmail.com> writes:
>
> On Tue, 22 Sep 2015, Przemysław Skrzyniarz wrote:
>
> The issues you found should better be reported to the progit community
> on GitHub: https://github.com/progit/progit
Next message, it means fourth I will send correctly group (of course and
I'll
I'm found one more mistake on page =>
https://git-scm.com/book/pl/v1/Rozproszony-Git-Rozproszone-przep%C5%82ywy-pracy
< In third line, before next to last line (Is: tryby => Should be:
trybu) in fourth part of text entitle "Przepływ pracy z dyktatorem i
porucznikami"(place in line - cit.: "... go d
On 22 Sep 2015, at 01:54, Eric Sunshine wrote:
> On Mon, Sep 21, 2015 at 7:03 PM, Lars Schneider
> wrote:
>> On 21 Sep 2015, at 20:09, Junio C Hamano wrote:
>>> larsxschnei...@gmail.com writes:
+test_expect_success 'init depot with UTF-16 encoded file and artificially
remove BOM' '
On 22 Sep 2015, at 03:10, Junio C Hamano wrote:
> Eric Sunshine writes:
>
>> Yes, it's because $d is a variable reference, even within double
>> quotes.
>
> s/even/especially/ ;-)
>
> Here is what I queued as SQUASH???
>
> diff --git a/t/t9825-git-p4-handle-utf16-without-bom.sh
> b/t/t9825
On Tue, 22 Sep 2015, Przemysław Skrzyniarz wrote:
> Hi,
>
> On page =>
> https://git-scm.com/book/pl/v1/Rozproszony-Git-Rozproszone-przep%C5%82ywy-pracy
> < I found typographical error in first line (Is: powala => Should be:
> pozwala) in third part of text entitle "Przepływ pracy z osobą integru
Hello all,
I've been playing with git-svn for some time already and as it seems to me
there are two most important problems which make it hard to use in production
for large repositories. Very low speed and large memory footprint of
synchronization with SVN repos (I am talking about clone and
Hi,
On page =>
https://git-scm.com/book/pl/v1/Rozproszony-Git-Rozproszone-przep%C5%82ywy-pracy
< I found typographical error in first line (Is: powala => Should be:
pozwala) in third part of text entitle "Przepływ pracy z osobą integrującą
zmiany".
And next line, it means third line at the bottom
87 matches
Mail list logo
