On 12/11/2018 9:15 AM, Konstantin Khomoutov wrote:
I think an uspoken issue here is that while you're indeed free to "fork"
this book and maintain your fork, having two books with almost identical
contents may not be the best option as it simply may be outright
confusing for those at whom you
ly in the early chapters, I suggest giving my version a try.
Since I'm giving away my version, you have nothing to loose except
perhaps a little time. If I'm right, and my version is clearer, then
you could benefit from it.
(You're a git expert so I doubt you need my version).
Cordially,
Jon Forrest
anges I've made, it's unlikely
that my changes would be accepted.
I do track the changes to the second edition of Pro Git and
incorporate that ones that still apply into my version.
But I hear what you're saying. Maybe if and when the third edition
of Pro Git comes out I'll tr
wrote. I hope you enjoy it.
The PDF of my version is at
https://drive.google.com/file/d/18wGebSU0dyYU1L_bfyoDQtZRF1Vo1H3p/view?usp=sharing
If there's enough interest, I'll try to put up an HTML version of
the book.
Cordially,
Jon Forrest
t, is to keep the same coverage
as upstream.
If they add something about Gitolite to their next edition, then
I will also.
Cordially,
Jon Forrest
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 7/26/2016 2:15 AM, Manlio Perillo wrote:
I have noted a problem when reading the PDF with Chromium: the
anchors/links do not work.
I see what you mean. I was able to replicate the problem with Acrobat
Reader on Windows 10. This seems to happen only with internal links - links
to external
in
different commit IDs each time.
Case closed.
Thanks, Jakub!
Jon Forrest
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Also, I realized one potentially major disadvantage of sharing in
Google Drive. This is that the URL will change each time I update
the book. Apparently Google is taking away the ability to create
a static link at the end of August 2016.
I think you can share a folder instead, and this would be
On 7/24/2016 11:51 AM, Rodrigo Campos wrote:
And what is the problem with that, if you are doing it with instructional
purposes? Let's assume that this helps and not confuses later when the commits
*do* change. What is the problem you face?
A lot of instructional material contains stuff like
On 7/24/2016 11:46 AM, Jakub Narębski wrote:
Please try to keep to the 80-character lines.
Sorry.
Another possibility is to set authordate and committerdate to some
specified time by the way of appropriate environment variables.
That sounds like a great idea. Assuming it
works the way I e
On 7/24/2016 11:27 AM, Jakub Narębski wrote:
In my opinion being able to view it online has its advantages.
Even casual reader can check it, and point errors or offer suggestions
for improvements.
Absolutely. Now that I've finished the editing I'll look
into that.
I think you can share a f
r instructional purposes only, and only when the committer
explicitly
chooses to use this option. I'm *not* proposing a general change to Git's
behavior.
Is such a thing to ridiculous to even consider? Is there a better way to
achieve the same result?
Jon Forrest
--
To unsubscribe
On 7/24/2016 10:19 AM, Jakub Narębski wrote:
As far as I can see you cannot view it online (without downloading).
True. I changed the way the HTML file is generated so that it
contains all the images downloading it is as good as viewing
it online. I'm not current with the thinking about the m
hhMm8
The complete self-contained HTML is at:
https://drive.google.com/file/d/0B-Llso12P94-U3g1aDBRWjk1Sk0
The sources for this book are at:
https://github.com/nobozo/progit2
I welcome comments.
Jon Forrest
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body
when the same repo is shared
by both Windows and *nix Git users over Dropbox or a shared filesystem?
Jon Forrest
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Windows.
Thanks for the quick (and correct) response.
Jon Forrest
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 5/20/2016 6:19 AM, Torsten Bögershausen wrote:
On 20.05.16 03:48, Jon Forrest wrote:
I'm running Git version 2.8.2 built from source on Ubuntu 16.04.
I'm using a repository that's stored on Dropbox. I'm the only person
accessing this repo. Everything works great.
For
epo to a non-Dropbox location, just in case
it was Dropbox that was causing the problem, but this didn't
make any difference.
(If you want to try this yourself, try it on the ProGit2
book source on Github).
Thanks,
Jon Forrest
--
To unsubscribe from this list: send the line "unsubscr
https://www.dropbox.com/s/4awq55350ef235m/progitreedited.en.pdf
and the source code is at
https://github.com/nobozo/progitreedited
I welcome your feedback. Please send any comments to me at
nob...@gmail.com. To make sure I recognize them as
comments about this book, please include [PGR] in the
subject.
Jon Forres
19 matches
Mail list logo