[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPA policy
From: |
Yuri Khan |
Subject: |
Re: ELPA policy |
Date: |
Mon, 9 Nov 2015 08:59:53 +0600 |
On Mon, Nov 9, 2015 at 7:45 AM, Dmitry Gutov <address@hidden> wrote:
> Still, the more happens in the repository, the harder it is to grasp or
> manage. Right now you can call 'git log' and see the most recent things that
> happened to Emacs master. Or do 'git pull', and call 'git diff' on the
> revision range that was printed out, and see all changes since your last
> update.
I almost wanted to mention that you can restrict “git log” and “git
diff” to a particular path in the repository, but realized it might
start a new git subthread.
(FWIW I also think separate repositories are better, as long as
development is mostly independent across the divide.)
- Re: ELPA policy, (continued)
- Re: ELPA policy, Artur Malabarba, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Artur Malabarba, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Dmitry Gutov, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Dmitry Gutov, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Richard Stallman, 2015/11/08
- Re: ELPA policy, Dmitry Gutov, 2015/11/08
- Re: ELPA policy,
Yuri Khan <=
- Re: ELPA policy, Artur Malabarba, 2015/11/08
- Re: ELPA policy, Stephen Leake, 2015/11/09
- Re: ELPA policy, David Kastrup, 2015/11/05
Re: Proposed new core library: pl.el, Artur Malabarba, 2015/11/05
Re: Proposed new core library: pl.el, Ted Zlatanov, 2015/11/05