[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: git history tracking across renames (and emacs support)
|
From: |
Noam Postavsky |
|
Subject: |
Re: git history tracking across renames (and emacs support) |
|
Date: |
Mon, 1 Jan 2018 17:45:17 -0500 |
unarchive 8756
reopen 8756
tags 8756 - patch
quit
On Mon, Jan 1, 2018 at 5:04 PM, Óscar Fuentes <address@hidden> wrote:
> Looking at those bug reports, I see that 19045 was created by me with a
> naive patch. Someone mentioned the more complete 8756 and then I closed
> 19045 without realizing that it has been merged with 8756, which was
> closed by the same command and so it remains to this day.
Okay, reopened.
Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el), Richard Stallman, 2018/01/01
- Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el), Paul Eggert, 2018/01/02
- Re: git history tracking across renames (and emacs support), Lars Ingebrigtsen, 2018/01/02
- Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el), Eli Zaretskii, 2018/01/02
- Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el), Paul Eggert, 2018/01/02
- Re: git history tracking across renames (and emacs support), Stefan Monnier, 2018/01/02
- Re: git history tracking across renames (and emacs support), Eli Zaretskii, 2018/01/03
- Re: git history tracking across renames (and emacs support), Stefan Monnier, 2018/01/03
- Re: git history tracking across renames (and emacs support), Eli Zaretskii, 2018/01/03