From: Steffen Daode Nurpmeso <sdaoden@googlemail.com>
To: git@vger.kernel.org
Subject: Jabber, question on push,pull and --tags, and no help but jabber
Date: Mon, 6 Jun 2011 15:02:05 +0200 [thread overview]
Message-ID: <20110606130205.GA41674@sherwood.local> (raw)
Hello GIT,
first paragraph is reserved for praising your existence.
'Used cvs(1) for long years in small team projects with local
private repos and never felt the need for anything else. 2011
is different. I first tried you but failed resoundingly. Due
to vim(1) and mutt(1) i discovered hg(1) and i still love it's
simple usage. 'Talking about the front-end anyway. It's huge
memory consumption and slow performance forbids it's usage on
our old PCs (e.g. Cyrix 166+) though. So i came back and
found you still receptive! And the more i work, the less
i hurt, the greater the knowledge, the smoother the
interaction. Are you the final word on RC in the end?
I stumbled over one thing i don't understand, because it seems
illogical: why do i need to use --tags to force pushing of tags?
Because there is even a config option for the latter, i suspect
this is because of intention. It would be nice to get some
information on the background of that, like a link to yet existing
documentation. Anyway i was a bit astonished to look at some
heavily scripted page of my free private repo webhoster :-) and
don't see any tags, even though i've pushed multiple times and
v0.0.0 was created directly after the first commit. I would *not*
have detected that otherwise ...
(Yes i know it's somewhat implied by 'git help push'..--tags.
But i'm blonde.)
Some more i'll pack into this so that it's gone with the wind:
- Due to my weak GPRS or noisy HDSPA radio connection here in the
pampa :) i hope for continuable network actions - failing after
98% is a costly pain. So it was a real joy to read somewhere
that a GSOC project will address this issue!!
- OpenSSL support for signing. I don't use PGP/GPG. But i use
HTTPS, POPS, SSH etc., so i'll have an OpenSSL/OpenSSH
environment here on my box ready to use.
Thanks for GIT!
--
Ciao, Steffen
sdaoden(*)(gmail.com)
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
next reply other threads:[~2011-06-06 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 13:02 Steffen Daode Nurpmeso [this message]
2011-06-06 14:31 ` Jabber, question on push,pull and --tags, and no help but jabber Michael J Gruber
2011-06-06 15:21 ` Felipe Contreras
2011-06-06 21:46 ` Steffen Daode Nurpmeso
2011-06-07 5:47 ` Michael J Gruber
2011-06-07 10:24 ` Steffen Daode Nurpmeso
[not found] ` <9215090.63086.1307370716794.JavaMail.trustmail@mail1.terreactive.ch>
2011-06-06 15:34 ` Victor Engmark
2011-06-06 17:58 ` Junio C Hamano
2011-06-07 10:48 ` [PATCH] Notes that tags need to pushed explicitely Steffen Daode Nurpmeso
2011-06-07 14:12 ` Junio C Hamano
2011-06-07 15:33 ` [PATCH] Remarks that tags need to be pushed explicitly Steffen Daode Nurpmeso
2011-06-10 20:39 ` [PATCH v2] " Steffen Daode Nurpmeso
2011-06-10 21:24 ` Junio C Hamano
2011-06-11 17:20 ` Steffen Daode Nurpmeso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110606130205.GA41674@sherwood.local \
--to=sdaoden@googlemail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).