From: Stephen & Linda Smith <ischis2@cox.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2018, #02; Tue, 11)
Date: Wed, 12 Sep 2018 04:39:34 -0700 [thread overview]
Message-ID: <8849662.cxaaR4pK4i@thunderbird> (raw)
In-Reply-To: 8951536.UanLVthjk7@thunderbird
On Wednesday, September 12, 2018 12:13:23 AM MST Junio C Hamano wrote:
> Stephen & Linda Smith <ischis2@cox.net> writes:
> > On Tuesday, September 11, 2018 3:20:19 PM MST Junio C Hamano wrote:
> >> * jc/wt-status-state-cleanup (2018-09-07) 1 commit
> >>
> >> - WIP: roll wt_status_state into wt_status and populate in the collect
> >>
> >> phase (this branch uses ss/wt-status-committable.)
> >>
> >> * ss/wt-status-committable (2018-09-07) 4 commits
> >>
> >> - wt-status.c: set the committable flag in the collect phase
> >> - t7501: add test of "commit --dry-run --short"
> >> - wt-status: rename commitable to committable
> >> - wt-status.c: move has_unmerged earlier in the file
> >> (this branch is used by jc/wt-status-state-cleanup.)
> >
> > I note that the jc/wt-status-state-cleanup branch is a patch "for
> > illustration purposes only" [1].
> >
> > I was about to update that patch to start dealing with the free() function
> > calls, but noted you added the patch. Do you want me to take that patch
> > and continue on? Or does someone else have something in progress?
>
> I do not plan to.
Ok ... from the wording I wasn't sure if there wasn't another developer
working this. I will pick up that patch and continue.
> In general, anything that is only in 'pu' is a
> fair game---when a better alternative appears, or a discussion leads
> to a conclusion that a change is unneeded, they are replaced and/or
> discarded. Just think of them as being kept slightly better record
> of existence than merely being in the list archive, nothing more.
Thanks that confirmed my reading of the Documentation/gitworkflows.txt.
next prev parent reply other threads:[~2018-09-12 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 2:36 What's cooking in git.git (Sep 2018, #02; Tue, 11) Stephen & Linda Smith
2018-09-12 7:13 ` Junio C Hamano
2018-09-12 11:39 ` Stephen & Linda Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-11 22:20 Junio C Hamano
2018-09-12 17:46 ` Ævar Arnfjörð Bjarmason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8849662.cxaaR4pK4i@thunderbird \
--to=ischis2@cox.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.