7 ms·

emacs is moving off of bzr.

by hyperbling 13y ago

deleted 13y ago
[deleted]
- Walkman 13y ago
  What are these then? https://github.com/git/git/blob/master/COPYING https://github.com/git/git/blob/master/COPYING https://github.com/git/git/blob/master/LGPL-2.1 https://github.com/git/git/blob/master/LGPL-2.1
  - leobelle 13y ago
    Yeah I was wrong. Thanks!
- nsmartt 13y ago
  > Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). https://github.com/git/git https://github.com/git/git
- reaperhulk 13y ago
  Git is (mostly) GPLv2. The other licenses, at least according to git's docs, are GPLv2 compatible.
- cheradenine01 13y ago
  Huh? Git is GPLv2.
- deleted 13y ago
  [deleted]
- philipn 13y ago
  git is licensed under the GPL (== v2), just not GPL (>= v2).
  - rainmaking 13y ago
    <smartass>logically impossible, you mean (== v2), just not GPL (> v2)</smartass>
- geocar 13y ago
  git is GPLv2 not GPLv2-or-any-later-version.
  - judk 13y ago
    GPLv2-or-layer is effectively GPLv2 plus recipient-friendly features. It is NOT suitable for the intended purpose of GPLv3, which adds restrictions on the recipient (for the benefit of 2nd-order recipients of derivatives).
  - judk 13y ago
    http://www.gnu.org/licenses/gpl-faq.html#VersionTwoOrLater http://www.gnu.org/licenses/gpl-faq.html#VersionTwoOrLater : GPLv2-or-layer is effectively GPLv2 plus recipient-friendly features. It is NOT fully suitable for the intended purpose of GPLv3, which adds restrictions on the recipient (for the benefit of 2nd-order recipients of derivatives). But it is better than GPLv2, and the best it can be without time travel. V2OrLater code can be incorporated in V3 code, but can also be incorporated in code that is less GNU-sense-of-Free than V3
- gcv 13y ago
  No, the project's leads have already approved the move to Git, and ESR is spearheading the (massive) effort involved.
  - Luyt 13y ago
    Indeed, ESR wrote this about it: http://esr.ibiblio.org/?p=5211 http://esr.ibiblio.org/?p=5211 "This is a brief heads-up that the reason I’ve been blog silent lately is that I’m concentrating hard on a sprint with what I consider a large payoff: getting the Emacs project fully converted to git. In retrospect, choosing Bazaar as DVCS was a mistake that has presented unnecessary friction costs to a lot of contributors. RMS gets this and we’re moving. I’m also talking with RMS about the possibility that it’s time to shoot Texinfo through the head and go with a more modern, Web-friendly master format. Oh, and time to abolish info entirely in favor of HTML. He’s not entirely convinced yet of this, but he’s listening." He's also involved in freeing code-repositories from their prisons, and porting them to other versioning systems, with the Reposurgeon. See https://gitorious.org/reposurgeon/ https://gitorious.org/reposurgeon/ "reposurgeon enables risky operations that version-control systems don’t want to let you do, such as (1) editing past comments and metadata, (2) excising commits, (3) coalescing commits, and (4) removing files and subtrees from repo history. The original motivation for reposurgeon was to clean up artifacts created by repository conversions. It also functions as a repository conversion tool. Supported VCSes include git, hg, bzr, and Subversion."

emacs is moving off of bzr.

deleted 13y ago

[deleted]

Walkman 13y ago
What are these then? https://github.com/git/git/blob/master/COPYING https://github.com/git/git/blob/master/COPYING https://github.com/git/git/blob/master/LGPL-2.1 https://github.com/git/git/blob/master/LGPL-2.1
- leobelle 13y ago
  Yeah I was wrong. Thanks!
nsmartt 13y ago
> Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). https://github.com/git/git https://github.com/git/git
reaperhulk 13y ago
Git is (mostly) GPLv2. The other licenses, at least according to git's docs, are GPLv2 compatible.
cheradenine01 13y ago
Huh? Git is GPLv2.
deleted 13y ago
[deleted]
philipn 13y ago
git is licensed under the GPL (== v2), just not GPL (>= v2).
- rainmaking 13y ago
  <smartass>logically impossible, you mean (== v2), just not GPL (> v2)</smartass>
geocar 13y ago
git is GPLv2 not GPLv2-or-any-later-version.
- judk 13y ago
  GPLv2-or-layer is effectively GPLv2 plus recipient-friendly features. It is NOT suitable for the intended purpose of GPLv3, which adds restrictions on the recipient (for the benefit of 2nd-order recipients of derivatives).
- judk 13y ago
  http://www.gnu.org/licenses/gpl-faq.html#VersionTwoOrLater http://www.gnu.org/licenses/gpl-faq.html#VersionTwoOrLater : GPLv2-or-layer is effectively GPLv2 plus recipient-friendly features. It is NOT fully suitable for the intended purpose of GPLv3, which adds restrictions on the recipient (for the benefit of 2nd-order recipients of derivatives). But it is better than GPLv2, and the best it can be without time travel. V2OrLater code can be incorporated in V3 code, but can also be incorporated in code that is less GNU-sense-of-Free than V3
gcv 13y ago
No, the project's leads have already approved the move to Git, and ESR is spearheading the (massive) effort involved.
- Luyt 13y ago
  Indeed, ESR wrote this about it: http://esr.ibiblio.org/?p=5211 http://esr.ibiblio.org/?p=5211 "This is a brief heads-up that the reason I’ve been blog silent lately is that I’m concentrating hard on a sprint with what I consider a large payoff: getting the Emacs project fully converted to git. In retrospect, choosing Bazaar as DVCS was a mistake that has presented unnecessary friction costs to a lot of contributors. RMS gets this and we’re moving. I’m also talking with RMS about the possibility that it’s time to shoot Texinfo through the head and go with a more modern, Web-friendly master format. Oh, and time to abolish info entirely in favor of HTML. He’s not entirely convinced yet of this, but he’s listening." He's also involved in freeing code-repositories from their prisons, and porting them to other versioning systems, with the Reposurgeon. See https://gitorious.org/reposurgeon/ https://gitorious.org/reposurgeon/ "reposurgeon enables risky operations that version-control systems don’t want to let you do, such as (1) editing past comments and metadata, (2) excising commits, (3) coalescing commits, and (4) removing files and subtrees from repo history. The original motivation for reposurgeon was to clean up artifacts created by repository conversions. It also functions as a repository conversion tool. Supported VCSes include git, hg, bzr, and Subversion."