git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Jul 2015, #07; Mon, 27)

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jul 31, 2015, 21:37 UTC
Message-ID
<20150731213716.GA488564@vauxhall.crustytoothpaste.net>
In-Reply-To
<vpqoaiu9dci.fsf@anie.imag.fr>
On Thu, Jul 30, 2015 at 11:58:05AM +0200, Matthieu Moy wrote:
Show 16 quoted lines
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 
> > On Mon, Jul 27, 2015 at 02:23:04PM -0700, Junio C Hamano wrote:
> >> * bc/object-id (2015-06-17) 10 commits
> > Is there anything I can do to make this series less painful (e.g. a
> > reroll or such)?
> 
> For the GSoC part, "Suggested 'pencils down' date" is August 17th. The
> "Firm 'pencils down date'" is on 21th, so things should stabilize.
> 
> On the "unify ref-listing commands" side, the big code movement is in
> kn/for-each-ref which should hit master soon, but there are other less
> intrusive series active.
> 
> (That doesn't really answer your question, but may be relevant
> information)

It's certainly helpful to know the timeline. I'm fine with waiting, but I anticipate that there will be pain when it finally goes into pu, and if there's anything I can do to minimize that, I'd like to.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: Matthieu Moy
Message 4 of 4 in “What's cooking in git.git (Jul 2015, #07; Mon, 27)”
  1. Junio C HamanoJul 27, 2015
  2. brian m. carlsonJul 30, 2015
  3. Matthieu MoyJul 30, 2015
  4. brian m. carlsonJul 31, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.