Personal/Business loan special offer at
5%. Minimum amount we can provide in the form of a loan is from 5,000 Pounds
and the maximum amount is 5,000,000 Pounds. If you are interested in receiving
financial assistance without fear, without worries and complete security;
Contact me today on this
Personal/Business loan special offer at
5%. Minimum amount we can provide in the form of a loan is from 5,000 Pounds
and the maximum amount is 5,000,000 Pounds. If you are interested in receiving
financial assistance without fear, without worries and complete security;
Contact me today on this
Signed-off-by: SZEDER Gábor
---
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 e087c4bf00..57f984340e 100644
--- a/contrib/completion/git-completion.bash
+++ b/contri
We’d like to contract your services for a period of 12 months. Please advise if
you are open to new opportunities.
Regards,
SAKI NISHIYO
For a long time already, we have tested Git's source code continuously 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 co
For a long time already, we have tested Git's source code continuously 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 co
"Johannes Schindelin via GitGitGadget"
writes:
> This patch series took wy more time than I had originally
> anticipated, but I think that in particular the advanced display of the test
> results and the reduction of the overall run time was worth it. Please let
> me know what you think a
Hi all,
On Wed, 23 Jan 2019, Johannes Schindelin via GitGitGadget wrote:
> * The Windows job was split into a job to build Git and 10 parallel
> jobs to run the test suite with the artifacts built by the first job.
> This reduces the overall run time from ~1h20 (which was the run time by
> th
For a long time already, we have tested Git's source code continuously 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 co
Hi Junio,
On Thu, 17 Jan 2019, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > ...
> > See the updated series:
> > https://public-inbox.org/git/pull.31.v3.git.gitgitgad...@gmail.com/
>
> Thanks.
>
> I see that you are already planning for v4, but I'll find time to
> take a look at w
Johannes Schindelin writes:
> ...
> See the updated series:
> https://public-inbox.org/git/pull.31.v3.git.gitgitgad...@gmail.com/
Thanks.
I see that you are already planning for v4, but I'll find time to
take a look at what is posted sometime this week anyway.
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 an
For a long time already, we have tested Git's source code continuously 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 co
> It is amazing to me how much my perspective changed when I actually had to
> teach Git to new users. Things that I live with easily all of a sudden
> become these unnecessarily confusing road blocks that make it *so hard* to
> actually use Git.
I see. Without the -y patch, this series looks good
Hi Stefan,
On Mon, 10 Dec 2018, Stefan Beller wrote:
> On Mon, Dec 10, 2018 at 2:08 PM Johannes Sixt wrote:
> >
> > Am 10.12.18 um 20:04 schrieb Johannes Schindelin via GitGitGadget:
> > > The idea was brought up by Paul Morelle.
> > >
> > > To be honest, this idea of rescheduling a failed exec
Hi Elijah,
On Mon, 10 Dec 2018, Elijah Newren wrote:
> On Mon, Dec 10, 2018 at 3:13 PM Johannes Schindelin via GitGitGadget
> wrote:
> >
> > The idea was brought up by Paul Morelle.
> >
> > To be honest, this idea of rescheduling a failed exec makes so much sense
> > that I wish we had done this
Stefan Beller writes:
> I wonder if it might be better to push this mechanism
> one layer down: Instead of having a flag that changes
> the behavior of the "exec" instructions and having a
> handy '-y' short cut for the new mode, we'd rather have
> a new type of command that executes&retries a co
On Mon, Dec 10, 2018 at 3:13 PM Johannes Schindelin via GitGitGadget
wrote:
>
> The idea was brought up by Paul Morelle.
>
> To be honest, this idea of rescheduling a failed exec makes so much sense
> that I wish we had done this from the get-go.
>
> So let's do the next best thing: implement a co
On Mon, Dec 10, 2018 at 1:18 PM Johannes Schindelin via GitGitGadget
wrote:
> The idea was brought up by Paul Morelle.
>
> To be honest, this idea of rescheduling a failed exec makes so much sense
> that I wish we had done this from the get-go.
>
> So let's do the next best thing: implement a co
On Mon, Dec 10, 2018 at 2:08 PM Johannes Sixt wrote:
>
> Am 10.12.18 um 20:04 schrieb Johannes Schindelin via GitGitGadget:
> > The idea was brought up by Paul Morelle.
> >
> > To be honest, this idea of rescheduling a failed exec makes so much sense
> > that I wish we had done this from the get-g
Am 10.12.18 um 20:04 schrieb Johannes Schindelin via GitGitGadget:
The idea was brought up by Paul Morelle.
To be honest, this idea of rescheduling a failed exec makes so much sense
that I wish we had done this from the get-go.
The status quo was actually not that bad a decision, because it ma
The idea was brought up by Paul Morelle.
To be honest, this idea of rescheduling a failed exec makes so much sense
that I wish we had done this from the get-go.
So let's do the next best thing: implement a command-line option and a
config setting to make it so.
The obvious intent behind that con
--
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.
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 promis
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 th
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 i
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 s
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 thos
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 contribut
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 bei
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 misunders
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
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 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 m
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 u
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 i
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 /usr/local/bin
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
Am lamia kindly reply me back so i can introduce my self to you.
Thanks
Lamia
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 eve
> 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.
Tha
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 an
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 p
> 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 pare
"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 tes
at no 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 f
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 rem
t 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 functionality.
However, I am curious whether there is a better way to check for the
presence of a local commit? Do
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 t
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 rem
Æ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 gitlab.com/g
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 lo
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 thei
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 upd
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 cor
Æ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 separ
gt; > > often
> > > timed out, or somehow the trigger did not work, and 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 woul
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
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 g
it allows 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.
(or whatever period that is), or do they offer
something special to git.git?
--
Duy
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
> dow
a time such that Travis will not time out?
To 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
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 -070
Do you need a loan? If YES Kindly contact us via:
citigrouploaninvestm...@aol.com
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 co
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
> > ph
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
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 co
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 th
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 th
I want us to join hands as partners because i have a deal for you.
I want us to join hands as partners because i have a deal for you.
I want us to join hands as partners because i have a deal for you
I want us to join hands as partners because i have a deal for you
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 th
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
>
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 not
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 143acd9417e.
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
>> > +++ b/D
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 2659153cb3
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
> > @@ -2
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
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 a/Docu
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 th
Col. Hussein Kharmusch
premjiazimhas...@outlook.com
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.
[...]
oth
> `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 more obvious
> seque
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
like
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
like
--
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,
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
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
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 w
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 conflict resolution I've be
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 `merge` command" to
> describe
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
1 file changed, 16 inser
ge
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 resche
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
1 - 100 of 255 matches
Mail list logo
