Loan Offer At 3% Interest Rate.

-- Do you need a loan for personal or business purpose? Bank Leumi offer a range of $20,000.00 to $25,000,000.00 at 3% interest rate. reply us if interested.

Re: [PATCH 5/5] index: offer advice for unknown index extensions

On Wed, Nov 21 2018, Jonathan Nieder wrote: > Junio C Hamano wrote: > >> This series has a strong smell of pushing back by the >> toolsmiths who refuse to promptly upgrade to help their users, and >> that is why I do not feel entirely happy with this series. > > Last reply, I

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Junio C Hamano writes: > I do not know if it makes sense to have 3 and 5 separate; I suspect > a single patch that does "clarify the warning, and allow those who > have no choice in which version of Git to choose squelch it" would > suffice. I actually do not mind two patches for these, but I

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Junio C Hamano writes: > As the deployed versions of Git will keep sending the wrong message, > I do not mind applying 1/5 and 2/5, given especially that Ben seems > to be OK with the plan. I however do not think 3 thru 5 is ready > yet with this round---there were some discussions on phrasing

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Junio C Hamano wrote: > Jonathan Nieder writes: >> I don't *think* you intend to say "sure, you got user reports, but >> (those users are wrong | those users are not real | you are not >> interpreting those users correctly)", but that is what I am hearing. > > What I have been saying is "we are

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Jonathan Nieder writes: > I don't *think* you intend to say "sure, you got user reports, but > (those users are wrong | those users are not real | you are not > interpreting those users correctly)", but that is what I am hearing. What I have been saying is "we are sending a wrong message to

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Junio C Hamano wrote: > Jonathan Nieder writes: >> Now, a meta point. Throughout this discussion, I have been hoping for >> some acknowledgement of the problem --- e.g. an "I am sympathetic to >> what you are trying to do, but ". I wasn't able to find that, and >> that is part of what

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Jonathan Nieder writes: > Now, a meta point. Throughout this discussion, I have been hoping for > some acknowledgement of the problem --- e.g. an "I am sympathetic to > what you are trying to do, but ". I wasn't able to find that, and > that is part of what contributed to the feeling of not

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Junio C Hamano wrote: > This series has a strong smell of pushing back by the > toolsmiths who refuse to promptly upgrade to help their users, and > that is why I do not feel entirely happy with this series. Last reply, I promise. :) This sentence might have the key to the

Re: [PATCH 5/5] index: offer advice for unknown index extensions

onathan Nieder wrote: > Junio C Hamano wrote: >> I am still puzzled by the insistence of 3/5 and this step that wants >> to kill the coalmine canary. But I am even more puzzled by the >> first two steps that want to disable the two optional extensions. [...] > I acknowledge your puzzlement. I'm

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Hi, Junio C Hamano wrote: > I am still puzzled by the insistence of 3/5 and this step that wants > to kill the coalmine canary. But I am even more puzzled by the > first two steps that want to disable the two optional extensions. > > What's so different this time with the new optional

Re: [PATCH 5/5] index: offer advice for unknown index extensions

Ben Peart writes: >> This message should say something like "Index uses the mandatory %s >> extension" to clarify and distinguish it from the below. We don't >> understand the upper-case one either, but the important distinction is >> that one is mandatory, and the other can be dropped. The two

Re: [PATCH 5/5] index: offer advice for unknown index extensions

On 11/20/2018 4:26 AM, Ævar Arnfjörð Bjarmason wrote: On Tue, Nov 20 2018, Jonathan Nieder wrote: Just commenting here on the end-state of this since it's easier than each patch at a time: First, do we still need to be doing %.4s instead of just %s? It would be easier for translators / to

Re: [PATCH 5/5] index: offer advice for unknown index extensions

On Tue, Nov 20 2018, Jonathan Nieder wrote: Just commenting here on the end-state of this since it's easier than each patch at a time: First, do we still need to be doing %.4s instead of just %s? It would be easier for translators / to understand what's going on if it were just %s. I.e. "this

[PATCH 5/5] index: offer advice for unknown index extensions

It is not unusual for multiple distinct versions of Git to act on a single repository. For example, some IDEs bundle a particular version of Git, which can be a different version from the system copy of Git, or on a Mac, /usr/bin/git quickly goes out of sync with the Homebrew git in

2% Loan Offer

Loans for all kind of purpose We offer from a minimum amount of 10,000.00 dollars to 20 million dollars And at a low interest rate of 2% Loan Term: 25 years maximum depending on the loan amount you need. Customers should be above the age of 18 This loan transaction is 100% guarantee for serious

BUSSINESS OFFER

Am lamia kindly reply me back so i can introduce my self to you. Thanks Lamia

Re: [PATCH v3 2/3] shallow: offer to prune only non-existing entries

Hi Jonathan, On Fri, 26 Oct 2018, Jonathan Tan wrote: > > So even better would be to use `is_promisor_object(oid) || > > has_object_file(oid)`, right? > > > > This is something that is probably not even needed: as I mentioned, > > the shallow commits are *expected* to be local. It should not

Re: [PATCH v3 2/3] shallow: offer to prune only non-existing entries

> Thanks for confirming. > > So even better would be to use `is_promisor_object(oid) || > has_object_file(oid)`, right? > > This is something that is probably not even needed: as I mentioned, the > shallow commits are *expected* to be local. It should not ever happen that > they are fetched.

Re: [PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

Hi Junio, On Thu, 25 Oct 2018, Junio C Hamano wrote: > "Johannes Schindelin via GitGitGadget" > writes: > > > For a long time already, we have Git's source code continuously tested via > > Travis CI, see e.g. https://travis-ci.org/git/git/builds/421738884. It has > > served us well, and more

Re: [PATCH v3 2/3] shallow: offer to prune only non-existing entries

Hi Jonathan, On Thu, 25 Oct 2018, Jonathan Tan wrote: > > On Wed, 24 Oct 2018, Johannes Schindelin wrote: > > > > Coming back to my question whether there is a better way to check for > > the presence of a local commit, I figured that I can use > > `has_object_file()` instead of looking up and

Re: [PATCH v3 2/3] shallow: offer to prune only non-existing entries

> On Wed, 24 Oct 2018, Johannes Schindelin wrote: > > > On Wed, 24 Oct 2018, Junio C Hamano wrote: > > > > > Jonathan, do you see any issues with the use of lookup_commit() in > > > this change wrt lazy clone? I am wondering what happens when the > > > commit in question is at, an immediate

Re: [PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

"Johannes Schindelin via GitGitGadget" writes: > For a long time already, we have Git's source code continuously tested via > Travis CI, see e.g. https://travis-ci.org/git/git/builds/421738884. It has > served us well, and more and more developers actually pay attention and > benefit from the

Re: [PATCH v3 2/3] shallow: offer to prune only non-existing entries

promised object can be a shallow > commit. The entire idea of a shallow commit is that it *is* present, but > none of its parents. > > Also, I would claim that the shallow feature does not make sense with lazy > clones, as lazy clones offer a superset of shallow clone's functionali

[PATCH v4 2/3] shallow: offer to prune only non-existing entries

From: Johannes Schindelin The `prune_shallow()` function wants a full reachability check to be completed before it goes to work, to ensure that all unreachable entries are removed from the shallow file. However, in the upcoming patch we do not even want to go that far. We really only need to

Re: [PATCH v3 2/3] shallow: offer to prune only non-existing entries

*is* present, but none of its parents. Also, I would claim that the shallow feature does not make sense with lazy clones, as lazy clones offer a superset of shallow clone's functionality. However, I am curious whether there is a better way to check for the presence of a local commit? Do w

Re: [PATCH v3 2/3] shallow: offer to prune only non-existing entries

Jonathan, do you see any issues with the use of lookup_commit() in this change wrt lazy clone? I am wondering what happens when the commit in question is at, an immediate parent of, or an immediate child of a promisor object. I _think_ this change won't make it worse for two features in playing

[PATCH v3 2/3] shallow: offer to prune only non-existing entries

From: Johannes Schindelin The `prune_shallow()` function wants a full reachability check to be completed before it goes to work, to ensure that all unreachable entries are removed from the shallow file. However, in the upcoming patch we do not even want to go that far. We really only need to

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

Ævar Arnfjörð Bjarmason writes: >> sites could do the same polling and mirroring. I am just too lazy >> to open a new account at yet another hosting site to add that for >> loop, but I may choose to when I am absolutely bored and nothing >> else to do ;-). > > Do you mind if I squat

Re: [PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

On Tue, Oct 16, 2018 at 4:55 AM Taylor Blau wrote: > > On Mon, Oct 15, 2018 at 04:55:25PM +0200, Johannes Schindelin wrote: > > Another really good reason for me to do this is that I can prod the Azure > > Pipelines team directly. And I even get an answer, usually within minutes. > > Which is a

Re: [PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

On Mon, Oct 15, 2018 at 07:22:15AM -0700, Taylor Blau wrote: > Would we like to abandon Travis as our main CI service for upstream > git.git, and build on Azure Pipelines only? It's not only about "upstream git.git", but also about contributors, who might have enabled Travis CI integration on

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

On Tue, Oct 16, 2018 at 6:50 AM Junio C Hamano wrote: > > Johannes Schindelin writes: > > > AFAIR Junio does not push to github.com/git/git, it is an automatic > > mirror. > > > > GitLab could easily do the same. > > It used to be in the early days but these days git/git and > gitster/git are

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

Johannes Schindelin writes: > AFAIR Junio does not push to github.com/git/git, it is an automatic > mirror. > > GitLab could easily do the same. It used to be in the early days but these days git/git and gitster/git are updated in a same for loop that pushes to various destinations. You are

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

Ævar Arnfjörð Bjarmason writes: > I have not reviewed this in any detail, but incorporating this in some > form or other seems like a no-brainer to me. > > If we have "free" (from the perspective of the project) CPU being > offered by various CI setups let's use it. Somebody else said in a

Re: [PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

d for security reasons > > > (the Windows builds are performed in a private pool of containers), the > > > Windows builds are completely disabled for Pull Requests on GitHub. > > > > This would be a concession of [1], in my mind: is it possible to run the > >

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

On Mon, Oct 15, 2018 at 8:33 PM Johannes Schindelin wrote: > > Hi team, > > On Mon, 15 Oct 2018, Christian Couder wrote: > > > On Mon, Oct 15, 2018 at 5:46 PM Duy Nguyen wrote: > > > > > > On Mon, Oct 15, 2018 at 5:08 PM Ævar Arnfjörð Bjarmason > > > wrote: > > > > As an aside I poked Junio via

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

Hi team, On Mon, 15 Oct 2018, Christian Couder wrote: > On Mon, Oct 15, 2018 at 5:46 PM Duy Nguyen wrote: > > > > On Mon, Oct 15, 2018 at 5:08 PM Ævar Arnfjörð Bjarmason > > wrote: > > > As an aside I poked Junio via private mail in late August to see if he'd > > > be interested in pushing to

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

ows gitlab forks to have CI support > from the beginning. But gitlab ci has time execution limits if I > remember correctly and I'm not sure if we'll use it all up before the > end of the month (or whatever period that is), or do they offer > something special to git.git? I can ask for more time if that would help.

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

tever period that is), or do they offer something special to git.git? -- Duy

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

On Mon, Sep 03 2018, Johannes Schindelin via GitGitGadget wrote: > As a special treat, this patch series adds the ability to present the > outcome of Git's test suite as JUnit-style .xml files. This allows the VSTS > build to present fun diagrams, trends, and makes it a lot easier to drill >

Re: [PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

o be honest, I spent such a lot of time to get things to work on Azure Pipelines, *and* we get a nice view on the test failures there, too (which Travis will probably also offer soon, in response to what Azure Pipelines offer ;-)), I cannot really justify spending time on trying to make things work o

Re: [PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

Hi Johannes, Thanks for putting this together, and offering to build Git on Azure Pipelines. I haven't followed v1 of this series very closely, so please excuse me if my comments have already been addressed, and I missed them in a skim of the last revision. On Mon, Oct 15, 2018 at 03:11:57AM

Loan Offer

Do you need a loan? If YES Kindly contact us via: citigrouploaninvestm...@aol.com

[PATCH v2 00/13] Offer to run CI/PR builds in Azure Pipelines

For a long time already, we have Git's source code continuously tested via Travis CI, see e.g. https://travis-ci.org/git/git/builds/421738884. It has served us well, and more and more developers actually pay attention and benefit from the testing this gives us. It is also an invaluable tool for

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

On Wed, Sep 5, 2018 at 12:02 PM Sebastian Schuberth wrote: > > On 9/3/2018 11:10 PM, Johannes Schindelin via GitGitGadget wrote: > > > The one sad part about this is the Windows support. Travis lacks it, and we > > work around that by using Visual Studio Team Services (VSTS) indirectly: one > >

Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

On 9/3/2018 11:10 PM, Johannes Schindelin via GitGitGadget wrote: The one sad part about this is the Windows support. Travis lacks it, and we work around that by using Visual Studio Team Services (VSTS) indirectly: one phase in Travis would trigger a build, wait for its log, and then paste that

[PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

For a long time already, we have Git's source code continuously tested via Travis CI, see e.g. https://travis-ci.org/git/git/builds/421738884. It has served us well, and more and more developers actually pay attention and benefit from the testing this gives us. It is also an invaluable tool for

[PATCH v6 15/21] range-diff: offer to dual-color the diffs

From: Johannes Schindelin When showing what changed between old and new commits, we show a diff of the patches. This diff is a diff between diffs, therefore there are nested +/- signs, and it can be relatively hard to understand what is going on. With the --dual-color option, the preimage and

[PATCH v5 15/21] range-diff: offer to dual-color the diffs

From: Johannes Schindelin When showing what changed between old and new commits, we show a diff of the patches. This diff is a diff between diffs, therefore there are nested +/- signs, and it can be relatively hard to understand what is going on. With the --dual-color option, the preimage and

partnership offer,

I want us to join hands as partners because i have a deal for you.

partnership offer,

I want us to join hands as partners because i have a deal for you.

partnership offer

I want us to join hands as partners because i have a deal for you

partnership offer

I want us to join hands as partners because i have a deal for you

[PATCH v4 15/21] range-diff: offer to dual-color the diffs

From: Johannes Schindelin When showing what changed between old and new commits, we show a diff of the patches. This diff is a diff between diffs, therefore there are nested +/- signs, and it can be relatively hard to understand what is going on. With the --dual-color option, the preimage and

Re: [PATCH] diff.c: offer config option to control ws handling in move detection

On Thu, Jul 19, 2018 at 10:32 AM Junio C Hamano wrote: > > Stefan Beller writes: > > > "git format-patch HEAD^ --color" produces red/green output > > (like git log would), so I do not see why --color-moved should impact > > format-patch differently. (i.e. if the user requests format-patch with >

Re: [PATCH] diff.c: offer config option to control ws handling in move detection

Stefan Beller writes: > "git format-patch HEAD^ --color" produces red/green output > (like git log would), so I do not see why --color-moved should impact > format-patch differently. (i.e. if the user requests format-patch with > color-moved we can do it, otherwise, when colors are off, we do

Re: [PATCH] diff.c: offer config option to control ws handling in move detection

On Thu, Jul 19, 2018 at 9:29 AM Junio C Hamano wrote: > > Stefan Beller writes: > > > On Wed, Jul 18, 2018 at 10:45 AM Junio C Hamano wrote: > >> > >> Stefan Beller writes: > >> > >> > diff --git a/Documentation/diff-options.txt > >> > b/Documentation/diff-options.txt > >> > index

Re: [PATCH] diff.c: offer config option to control ws handling in move detection

Stefan Beller writes: > On Wed, Jul 18, 2018 at 10:45 AM Junio C Hamano wrote: >> >> Stefan Beller writes: >> >> > diff --git a/Documentation/diff-options.txt >> > b/Documentation/diff-options.txt >> > index 143acd9417e..8da7fed4e22 100644 >> > --- a/Documentation/diff-options.txt >> > +++

[PATCH 10/10] diff.c: offer config option to control ws handling in move detection

Signed-off-by: Stefan Beller --- Documentation/config.txt | 5 + Documentation/diff-options.txt | 7 +-- diff.c | 9 + 3 files changed, 19 insertions(+), 2 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index

Re: [PATCH] diff.c: offer config option to control ws handling in move detection

On Wed, Jul 18, 2018 at 10:45 AM Junio C Hamano wrote: > > Stefan Beller writes: > > > diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt > > index 143acd9417e..8da7fed4e22 100644 > > --- a/Documentation/diff-options.txt > > +++ b/Documentation/diff-options.txt > > @@

Re: [PATCH] diff.c: offer config option to control ws handling in move detection

Stefan Beller writes: > diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt > index 143acd9417e..8da7fed4e22 100644 > --- a/Documentation/diff-options.txt > +++ b/Documentation/diff-options.txt > @@ -294,8 +294,11 @@ dimmed_zebra:: > > --color-moved-ws=:: > This

[PATCH] diff.c: offer config option to control ws handling in move detection

Signed-off-by: Stefan Beller --- This is the cherry on the cake named sb/diff-color-move-more. Documentation/config.txt | 5 + Documentation/diff-options.txt | 7 +-- diff.c | 9 + 3 files changed, 19 insertions(+), 2 deletions(-) diff --git

[PATCH v3 15/20] range-diff: offer to dual-color the diffs

From: Johannes Schindelin When showing what changed between old and new commits, we show a diff of the patches. This diff is a diff between diffs, therefore there are nested +/- signs, and it can be relatively hard to understand what is going on. With the --dual-color option, the preimage and

I am Mr. Hussein Harmuh from Syria. I got my information while I was searching a trusted person, I have a very profitable business offer for you and I can assure you that you will not regret being par

Col. Hussein Kharmusch

Donation offer

premjiazimhas...@outlook.com

Re: [PATCH v9 00/17] rebase -i: offer to recreate commit topology by rebasing merges

This has been sent by mistake, I'm sorry, please disregard. Sergey Organov writes: > Johannes Schindelin writes: > >> Junio, I think this is now ready for `next`. Thank you for your patience >> and help with this. [...]

Re: [PATCH v9 00/17] rebase -i: offer to recreate commit topology by rebasing merges

ies on top of current `master`, i.e. both > `pw/rebase-keep-empty-fixes` and `pw/rebase-signoff`, to resolve merge > conflicts myself. > > > Johannes Schindelin (15): > sequencer: avoid using errno clobbered by rollback_lock_file() > sequencer: make rearrange_squash() a bit mor

[PATCH v2 15/18] branch-diff: offer to dual-color the diffs

When showing what changed between old and new commits, we show a diff of the patches. This diff is a diff between diffs, therefore there are nested +/- signs, and it can be relatively hard to understand what is going on. With the --dual-color option, the preimage and the postimage are colored

[PATCH 15/18] branch-diff: offer to dual-color the diffs

When showing what changed between old and new commits, we show a diff of the patches. This diff is a diff between diffs, therefore there are nested +/- signs, and it can be relatively hard to understand what is going on. With the --dual-color option, the preimage and the postimage are colored

Account Receivables (Job Offer)

-- We are interested in employing you to represent our company in the United States and Canada for the position of a Collection Agent to our Company Yokohama Rubber Company Limited Japan, you will be on a 20% commission for the amount owed and collected on our behalf from our customers,

[PATCH v7 01/12] argv_array: offer to split a string by whitespace

This is a simple function that will interpret a string as a whitespace delimited list of values, and add those values into the array. Note: this function does not (yet) offer to split by arbitrary delimiters, or keep empty values in case of runs of whitespace, or de-quote Unix shell style. All fo

[PATCH v6 01/11] argv_array: offer to split a string by whitespace

This is a simple function that will interpret a string as a whitespace delimited list of values, and add those values into the array. Note: this function does not (yet) offer to split by arbitrary delimiters, or keep empty values in case of runs of whitespace, or de-quote Unix shell style. All fo

Re: Great Investment Offer

Hello In my search for a business partner i got your contact in google search. My client is willing to invest $10 Million to $500 million but my client said he need a trusted partner who he can have a meeting at the point of releasing his funds. I told my client that you have a good profile

Re: [PATCH v9 00/17] rebase -i: offer to recreate commit topology by rebasing merges

Junio C Hamano writes: >> - Rebased the patch series on top of current `master`, i.e. both >> `pw/rebase-keep-empty-fixes` and `pw/rebase-signoff`, to resolve merge >> conflicts myself. > > Good to see the last item, as this gave me a chance to make sure > that the

Re: [PATCH v9 00/17] rebase -i: offer to recreate commit topology by rebasing merges

Johannes Schindelin writes: > Changes since v8: > > - Disentangled the patch introducing `label`/`reset` from the one > introducing `merge` again (this was one stupid, tired `git commit > --amend` too many). > > - Augmented the commit message of "introduce the

[PATCH v9 04/17] sequencer: offer helpful advice when a command was rescheduled

Previously, we did that just magically, and potentially left some users quite puzzled. Let's err on the safe side instead, telling the user what is happening, and how they are supposed to continue. Signed-off-by: Johannes Schindelin --- sequencer.c | 16

[PATCH v9 00/17] rebase -i: offer to recreate commit topology by rebasing merges

conflicts myself. Johannes Schindelin (15): sequencer: avoid using errno clobbered by rollback_lock_file() sequencer: make rearrange_squash() a bit more obvious sequencer: refactor how original todo list lines are accessed sequencer: offer helpful advice when a command was rescheduled

[PATCH v5 01/11] argv_array: offer to split a string by whitespace

This is a simple function that will interpret a string as a whitespace delimited list of values, and add those values into the array. Note: this function does not (yet) offer to split by arbitrary delimiters, or keep empty values in case of runs of whitespace, or de-quote Unix shell style. All fo

Re: [PATCH v4 01/11] argv_array: offer to split a string by whitespace

Junio C Hamano writes: > Johannes Schindelin writes: > >> +void argv_array_split(struct argv_array *array, const char *to_split) >> +{ >> +while (isspace(*to_split)) >> +to_split++; >> +for (;;) { >> +const char *p =

Re: [PATCH v4 01/11] argv_array: offer to split a string by whitespace

Johannes Schindelin writes: > +void argv_array_split(struct argv_array *array, const char *to_split) > +{ > + while (isspace(*to_split)) > + to_split++; > + for (;;) { > + const char *p = to_split; > + > + if (!*p) > +

Re: Fw: New Defects reported by Coverity Scan for git [argv_array: offer to split a string by whitespace]

Hi Philip, On Sun, 22 Apr 2018, Philip Oakley wrote: > is this part of your series "argv_array: offer to split a string by > whitespace"? > > https://public-inbox.org/git/capig+ctdbttuefymkntm773ebge14tpic4g4xefusvwsypd...@mail.gmail.com/ > > - Original

[PATCH v8 04/16] sequencer: offer helpful advice when a command was rescheduled

Previously, we did that just magically, and potentially left some users quite puzzled. Let's err on the safe side instead, telling the user what is happening, and how they are supposed to continue. Signed-off-by: Johannes Schindelin --- sequencer.c | 16

[PATCH v8 00/16] rebase -i: offer to recreate commit topology by rebasing merges

a bit more obvious sequencer: refactor how original todo list lines are accessed sequencer: offer helpful advice when a command was rescheduled sequencer: introduce the `merge` command sequencer: fast-forward `merge` commands, if possible rebase-helper --make-script: introduce a flag to reb

[PATCH v4 01/11] argv_array: offer to split a string by whitespace

This is a simple function that will interpret a string as a whitespace delimited list of values, and add those values into the array. Note: this function does not (yet) offer to split by arbitrary delimiters, or keep empty values in case of runs of whitespace, or de-quote Unix shell style. All fo

Re: [PATCH v3 01/11] argv_array: offer to split a string by whitespace

se values into the array. > > > > Note: this function does not (yet) offer to split by arbitrary delimiters, > > or keep empty values in case of runs of whitespace, or de-quote Unix shell > > style. All fo this functionality can be added later, when and if needed. > > &g

Re: [PATCH v3 01/11] argv_array: offer to split a string by whitespace

On Fri, Apr 20, 2018 at 3:20 PM, Johannes Schindelin <johannes.schinde...@gmx.de> wrote: > This is a simple function that will interpret a string as a whitespace > delimited list of values, and add those values into the array. > > Note: this function does not (yet) offer to

[PATCH v3 01/11] argv_array: offer to split a string by whitespace

This is a simple function that will interpret a string as a whitespace delimited list of values, and add those values into the array. Note: this function does not (yet) offer to split by arbitrary delimiters, or keep empty values in case of runs of whitespace, or de-quote Unix shell style. All fo

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

On Fri, Apr 20, 2018 at 1:26 AM, Johannes Schindelin wrote: > Hi Jake, > > On Thu, 19 Apr 2018, Jacob Keller wrote: > >> On Wed, Apr 18, 2018 at 9:24 PM, Sergey Organov wrote: >> > Johannes Schindelin writes: >> > >> >>

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

Hi Jake, On Thu, 19 Apr 2018, Jacob Keller wrote: > On Wed, Apr 18, 2018 at 9:24 PM, Sergey Organov wrote: > > Johannes Schindelin writes: > > > >> On Fri, 13 Apr 2018, Phillip Wood wrote: > >> > >>> On 12/04/18 23:02, Johannes Schindelin wrote:

[PATCH v7 04/17] sequencer: offer helpful advice when a command was rescheduled

Previously, we did that just magically, and potentially left some users quite puzzled. Let's err on the safe side instead, telling the user what is happening, and how they are supposed to continue. Signed-off-by: Johannes Schindelin --- sequencer.c | 16

[PATCH v7 00/17] rebase -i: offer to recreate commit topology

!). Johannes Schindelin (15): sequencer: avoid using errno clobbered by rollback_lock_file() sequencer: make rearrange_squash() a bit more obvious sequencer: refactor how original todo list lines are accessed sequencer: offer helpful advice when a command was rescheduled sequencer: introduc

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

Hi Jacob, Jacob Keller writes: > On Wed, Apr 18, 2018 at 9:24 PM, Sergey Organov wrote: >> Johannes Schindelin writes: >> >>> Hi Phillip, >>> >>> On Fri, 13 Apr 2018, Phillip Wood wrote: >>> On 12/04/18 23:02,

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

On Wed, Apr 18, 2018 at 9:24 PM, Sergey Organov wrote: > Johannes Schindelin writes: > >> Hi Phillip, >> >> On Fri, 13 Apr 2018, Phillip Wood wrote: >> >>> On 12/04/18 23:02, Johannes Schindelin wrote: >>> > >>> > [...] >>> > >>> > So: the order of

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

Johannes Schindelin writes: > Hi Phillip, > > On Fri, 13 Apr 2018, Phillip Wood wrote: > >> On 12/04/18 23:02, Johannes Schindelin wrote: >> > >> > [...] >> > >> > So: the order of the 3-way merges does matter. >> > >> > [...] >> >> Those conflicts certainly look

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

Hi Jacob, Jacob Keller writes: > On Wed, Apr 11, 2018 at 10:42 PM, Sergey Organov wrote: >> Hi Jacob, >> >> Jacob Keller writes: >>> On Wed, Apr 11, 2018 at 6:13 AM, Sergey Organov wrote: It was

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

Hi Phillip, On Fri, 13 Apr 2018, Phillip Wood wrote: > On 12/04/18 23:02, Johannes Schindelin wrote: > > > > [...] > > > > So: the order of the 3-way merges does matter. > > > > [...] > > Those conflicts certainly look intimidating (and the ones in your later > reply with the N way merge

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

On 12/04/18 23:02, Johannes Schindelin wrote: Hi Jake, On Thu, 12 Apr 2018, Jacob Keller wrote: On Wed, Apr 11, 2018 at 10:42 PM, Sergey Organov wrote: Jacob Keller writes: On Wed, Apr 11, 2018 at 6:13 AM, Sergey Organov

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

t; > the original merge commit being the center of a chandelier, and each arm > > representing one of the N-1 merge heads with their own merge bases. > > > > I think this approach sounds reasonable. ... and it would incidentally also offer a saner way to do octopus m

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

On Thu, Apr 12, 2018 at 3:02 PM, Johannes Schindelin wrote: > Hi Jake, > > On Thu, 12 Apr 2018, Jacob Keller wrote: > >> On Wed, Apr 11, 2018 at 10:42 PM, Sergey Organov wrote: >> > >> > Jacob Keller writes: >> >> On Wed,

Re: [PATCH v6 00/15] rebase -i: offer to recreate commit topology

Hi Jake, On Thu, 12 Apr 2018, Jacob Keller wrote: > On Wed, Apr 11, 2018 at 10:42 PM, Sergey Organov wrote: > > > > Jacob Keller writes: > >> On Wed, Apr 11, 2018 at 6:13 AM, Sergey Organov wrote: > >>> It was rather

  1   2   3   >