On Mon, Nov 12, 2018 at 07:46:14AM -0800, Elijah Newren wrote:
> So maybe my commit message should have been something
> more like:
>
> """
> Knowing the original names (hashes) of commits can sometimes enable
> post-filtering that would otherwise be difficult or impossible. In
> particular,
On Mon, Nov 12, 2018 at 4:53 AM Jeff King wrote:
> On Sun, Nov 11, 2018 at 12:32:22AM -0800, Elijah Newren wrote:
>
> > > > Documentation/git-fast-export.txt | 7 +++
> > > > builtin/fast-export.c | 20 +++-
> > > > fast-import.c | 17
On Sun, Nov 11, 2018 at 12:32:22AM -0800, Elijah Newren wrote:
> > > Documentation/git-fast-export.txt | 7 +++
> > > builtin/fast-export.c | 20 +++-
> > > fast-import.c | 17 +
> > > t/t9350-fast-export.sh| 17
On Sat, Nov 10, 2018 at 11:20 PM Jeff King wrote:
>
> On Sat, Nov 10, 2018 at 10:23:11PM -0800, Elijah Newren wrote:
>
> > Knowing the original names (hashes) of commits, blobs, and tags can
> > sometimes enable post-filtering that would otherwise be difficult or
> > impossible. In particular,
On Sat, Nov 10, 2018 at 10:23:11PM -0800, Elijah Newren wrote:
> Knowing the original names (hashes) of commits, blobs, and tags can
> sometimes enable post-filtering that would otherwise be difficult or
> impossible. In particular, the desire to rewrite commit messages which
> refer to other
Knowing the original names (hashes) of commits, blobs, and tags can
sometimes enable post-filtering that would otherwise be difficult or
impossible. In particular, the desire to rewrite commit messages which
refer to other prior commits (on top of whatever other filtering is
being done) is very
6 matches
Mail list logo
