From: Michael Haggerty <mhagger@alum.mit.edu>
To: supadhyay <supadhyay@imany.com>
Cc: git@vger.kernel.org
Subject: Re: Tags/Branches missing in GIT
Date: Wed, 18 Apr 2012 22:43:13 +0200 [thread overview]
Message-ID: <4F8F2761.80904@alum.mit.edu> (raw)
In-Reply-To: <1334737624705-7476181.post@n2.nabble.com>
On 04/18/2012 10:27 AM, supadhyay wrote:
> My apologize. I have edit my subscription for users,issues and announce but
> not able to post any query or new topic . On their webpage I can not see any
> link/button for post new topic or etc. If you can guide me how ot post new
> topic there then it would be great help for me.
This is also explained in the FAQ [1].
Michael
[1] http://cvs2svn.tigris.org/faq.html#subscribing
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
prev parent reply other threads:[~2012-04-18 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 5:54 Tags/Branches missing in GIT supadhyay
2012-04-18 7:34 ` Michael Haggerty
2012-04-18 8:27 ` supadhyay
2012-04-18 20:43 ` Michael Haggerty [this message]
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=4F8F2761.80904@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=supadhyay@imany.com \
/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).