From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: interfacing M$-TFS
Date: Fri, 3 Dec 2010 22:01:39 +0100 [thread overview]
Message-ID: <20101203210139.GB14508@nibiru.local> (raw)
Hi folks,
is there any way for directly interfacing M$-TFS (w/o its svn proxy) ?
I'm currently working on an embedded linux project and my customer
has a company wide policy to put everything into - please put on
you intellectual seatbelt - M$ TFS.
Needless to mention that TFS' VCS stuff is practically unusable,
but some collegues still committing directly to TFS (haven't
conviced them to switch over to git), and releases have to be
put there, as QA folks dont know anything else.
My current workflow is:
#1: a main branch, frequently copied over TFS manually (;-o)
#2: lots of topic branches which get rebased onto master
#3: finished topic branches are rebased to latest master and
then copied over to and committed in TFS
Of course, that much manual work - especially with the need of
checking out / locking invidual files in TFS - really suxx and
wastes a lot of time. So I'm looking for way to:
a) track remote branches from TFS
b) push back changes into a TFS remote tracking branch
Both should be possible from Linux side, using the native protocol
(very unlikely that IT department can be convinced to install the
svn proxy for TFS).
thx
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next reply other threads:[~2010-12-03 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 21:01 Enrico Weigelt [this message]
2010-12-07 1:20 ` interfacing M$-TFS Neal Kreitzinger
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=20101203210139.GB14508@nibiru.local \
--to=weigelt@metux.de \
--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).