From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, David Barr <david.barr@cordelta.com>,
Ramkumar Ramachandra <artagnon@gmail.com>
Subject: jn/svn-fe (Re: What's cooking in git.git (Jan 2011, #01; Tue, 4))
Date: Tue, 4 Jan 2011 18:01:58 -0600 [thread overview]
Message-ID: <20110105000157.GA3138@burratino> (raw)
In-Reply-To: <7vipy4dy8y.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> * jn/svn-fe (2010-12-06) 18 commits
> - vcs-svn: Allow change nodes for root of tree (/)
> - vcs-svn: Implement Prop-delta handling
> - vcs-svn: Sharpen parsing of property lines
> - vcs-svn: Split off function for handling of individual properties
> - vcs-svn: Make source easier to read on small screens
> - vcs-svn: More dump format sanity checks
> - vcs-svn: Reject path nodes without Node-action
> - vcs-svn: Delay read of per-path properties
> - vcs-svn: Combine repo_replace and repo_modify functions
> - vcs-svn: Replace = Delete + Add
> - vcs-svn: handle_node: Handle deletion case early
> - vcs-svn: Use mark to indicate nodes with included text
> - vcs-svn: Unclutter handle_node by introducing have_props var
> - vcs-svn: Eliminate node_ctx.mark global
> - vcs-svn: Eliminate node_ctx.srcRev global
> - vcs-svn: Check for errors from open()
> - vcs-svn: Allow simple v3 dumps (no deltas yet)
> - vcs-svn: Error out for v3 dumps
>
> Some RFC patches, to give them early and wider exposure. Perhaps drop
> these during the -rc period?
The bottom one is a useful bugfix (to get an error message instead of
succeeding with nonsensical mode and blobs when the user tries to
import a --deltas dump) and should ideally be applied for v1.7.4.
The rest are a new feature (a surprisingly non-buggy one) and I don't
mind if you drop them.
next prev parent reply other threads:[~2011-01-05 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 23:50 What's cooking in git.git (Jan 2011, #01; Tue, 4) Junio C Hamano
2011-01-05 0:01 ` Jonathan Nieder [this message]
2011-01-05 2:11 ` Martin von Zweigbergk
2011-01-08 18:40 ` Ramsay Jones
2011-01-08 19:47 ` Johannes Sixt
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=20110105000157.GA3138@burratino \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=david.barr@cordelta.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).