From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: tarun patanwar <patanwar.tarun@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: GIT Integration with Siebel
Date: Tue, 5 Jul 2016 12:02:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1607051200590.8378@virtualbox> (raw)
In-Reply-To: <CAKK2_6ezVLd4ZMa4ToKZYq1Ab0Y5w3VJqj_8-BsUCj8Gf8f+ig@mail.gmail.com>
Hi Tarun,
On Tue, 5 Jul 2016, tarun patanwar wrote:
> We are trying to integrate GIT with Siebel 8.1 for source code control.
> We are not able to progress further since there seems to be no
> documentation available for the same.
Would you kindly explain what Siebel is, and what purpose the batch file
you want to adapt is supposed to serve?
Ciao,
Johannes
next prev parent reply other threads:[~2016-07-05 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 9:17 GIT Integration with Siebel tarun patanwar
2016-07-05 10:02 ` Johannes Schindelin [this message]
2016-07-05 10:19 ` tarun patanwar
2016-07-05 11:28 ` Johannes Schindelin
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=alpine.DEB.2.20.1607051200590.8378@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=patanwar.tarun@gmail.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).