[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Git transition checklist
|
From: |
Andreas Schwab |
|
Subject: |
Re: Git transition checklist |
|
Date: |
Wed, 08 Jan 2014 20:11:54 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Glenn Morris <address@hidden> writes:
> There's simplicity, and the issue that one day a file/package may move
> from one to the other.
You can just add another remote to your clone that points to the elpa
repository. Git doesn't really care where the commits originate from,
once they are in your repository all are alike.
Andreas.
--
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- Re: Git transition checklist, (continued)
- Re: Git transition checklist, Eric S. Raymond, 2014/01/08
- Re: Git transition checklist, Andreas Schwab, 2014/01/08
- Re: Git transition checklist, Glenn Morris, 2014/01/08
- Re: Git transition checklist, Stefan Monnier, 2014/01/08
- Re: Git transition checklist, Glenn Morris, 2014/01/08
- Re: Git transition checklist, Stefan Monnier, 2014/01/08
- Re: Git transition checklist,
Andreas Schwab <=
- Re: Git transition checklist, Glenn Morris, 2014/01/08
- Re: Git transition checklist, Stefan Monnier, 2014/01/08
- Re: Git transition checklist, Dani Moncayo, 2014/01/08
- Re: Git transition checklist, Bob Proulx, 2014/01/12
- Re: Git transition checklist, Bastien, 2014/01/13
Re: Git transition checklist, Bastien, 2014/01/08
Re: Git transition checklist, Glenn Morris, 2014/01/08