bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Bug-cvs Digest, Vol 27, Issue 9


From: Ather Adil
Subject: RE: Bug-cvs Digest, Vol 27, Issue 9
Date: Thu, 20 Apr 2006 17:44:04 +0530

Hi Friends,
I am facing a problem in locking the file in trunk and is getting locked
for branch also.

Trunk revision of a file is 1.1
Branch revison is 1.1.1.1

Please help me
Regards,
Ather

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
address@hidden
Sent: Wednesday, April 19, 2006 9:37 PM
To: address@hidden
Subject: Bug-cvs Digest, Vol 27, Issue 9

Send Bug-cvs mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.nongnu.org/mailman/listinfo/bug-cvs
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bug-cvs digest..."


Today's Topics:

   1. Re: shell version of log.pl  (Mark D. Baushke)
   2. Re: C99 strto* protos (Derek R. Price)
   3. Re: shell version of log.pl (Jim Hyslop)
   4. Re: merging the same version again and again and again and
      again and ... (Ingolf Steinbach)
   5. Re: C99 strto* protos (Eric Blake)


----------------------------------------------------------------------

Message: 1
Date: Tue, 18 Apr 2006 09:09:04 -0700
From: "Mark D. Baushke" <address@hidden>
Subject: Re: shell version of log.pl 
To: Jan Schaumann <address@hidden>
Cc: bug-cvs <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jan Schaumann <address@hidden> writes:

> "Mark D. Baushke" <address@hidden> wrote:
>  
> > Your attachments seem to be getting lost. Your PGP signature is
failing
> > and no attachment is present.
> 
> This is the first time in over 5 years I ever heard that.  If I sent
> myself the same message (with attachment and all), everything works
just
> fine.  Are you sure there isn't some setting in your mail client?

Yes. I suspect that the address@hidden gateway is where attachments are
getting stripped...

> Oh well, here you go inline, then:
> 
> ---8<------8<------8<-------
...script elided...
> ---8<------8<------8<-------

I have it now and your PGP signature verified correctly this time.

I have committed the script to the CVS repository as contrib/cvslog.sh

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFERQ8gCg7APGsDnFERAn8MAJ9SgMGGaT1zY7TfR/OcO2k1ithPhwCgwH1D
hQBcP/gMhn9B8FJy5C8TeFg=
=NWaF
-----END PGP SIGNATURE-----




------------------------------

Message: 2
Date: Tue, 18 Apr 2006 13:24:31 -0400
From: "Derek R. Price" <address@hidden>
Subject: Re: C99 strto* protos
To: address@hidden
Cc: bug-cvs <address@hidden>, "Mark D. Baushke" <address@hidden>,
        Paul Eggert <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Derek R. Price wrote:

> 2006-04-11  Derek Price  <address@hidden>
>             Paul Eggert  <address@hidden>
> 
>         * lib/inttypes.h: New file.
>         * lib/strtoimax.c: Assume <inttypes.h>.
>         * m4/_inttypes_h.m4, m4/full-header-path.m4, m4/include_next:
New
>         files.
>         * modules/inttypes: New file.
>         * modules/strtoimax, modules/strtoumax: Depend on inttypes.


No one has objected in about a week and this patch plus a small typo fix
in m4/full-header-path.m4 is passing CVS nightly testing on some dozen
platforms, so I committed it to GNULIB.

Regards,

Derek
- --
Derek R. Price
CVS Solutions Architect
Ximbiot <http://ximbiot.com>
v: +1 717.579.6168
f: +1 717.234.3125
<address@hidden>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFERSDOLD1OTBfyMaQRAo7FAKC2Rgj9O7ci9hnMOqup5la2XADrwQCgn2k9
CikTM5BU1hA6ab99TkyYxcE=
=ccks
-----END PGP SIGNATURE-----




------------------------------

Message: 3
Date: Tue, 18 Apr 2006 18:35:29 -0400
From: Jim Hyslop <address@hidden>
Subject: Re: shell version of log.pl
To: "Mark D. Baushke" <address@hidden>
Cc: bug-cvs <address@hidden>, Jan Schaumann <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark D. Baushke wrote:
> Jan Schaumann <address@hidden> writes:
> 
> 
>>>"Mark D. Baushke" <address@hidden> wrote:
>>> 
>>>
>>>>Your attachments seem to be getting lost. Your PGP signature is
failing
>>>>and no attachment is present.
>>>
>>>This is the first time in over 5 years I ever heard that.  If I sent
>>>myself the same message (with attachment and all), everything works
just
>>>fine.  Are you sure there isn't some setting in your mail client?
> 
> 
> Yes. I suspect that the address@hidden gateway is where attachments
are
> getting stripped...

Probably. I was seeing the same behaviour - no attachments, and a bad
signature, and I'm using a different client (Thunderbird).

> I have it now and your PGP signature verified correctly this time.
Ditto.

- --
Jim Hyslop
Dreampossible: Better software. Simply.     http://www.dreampossible.ca
                 Consulting * Mentoring * Training in
    C/C++ * OOD * SW Development & Practices * Version Management
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFERWmxLdDyDwyJw+MRAqx6AKCO35L+qBYSO3v9iAMzyMkN9bKx7QCgqTaj
b3k+gDgdhbVkuXq7xTLAYZw=
=H8N5
-----END PGP SIGNATURE-----





------------------------------

Message: 4
Date: Wed, 19 Apr 2006 09:14:47 +0200
From: Ingolf Steinbach <address@hidden>
Subject: Re: merging the same version again and again and again and
        again and ...
To: Harald Dunkel <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Harald Dunkel wrote:
[...]
> % cvs update -j cde2006_hop1 README
> RCS file: /sceng/cvsroot_cde/config/README,v
> retrieving revision 1.31.4.3
> retrieving revision 1.31.4.3.2.13
> Merging differences between 1.31.4.3 and 1.31.4.3.2.13 into README
[...]

Could you please send us the output of

% cvs diff -r1.31.4.3 -r1.31.4.3.2.13 README

I could imagine that they are identical. Is that right?

With your cvs update command, you state that you want to
merge the changes from the cde2006_hop1 branch into your
working copy. There have been changes to the README file
in that branch (13 revisions). These changes are then
merged into your local README. It does not matter that
the 13th revision in that branch is the same as the original
version.

Kind regards
     Ingolf
-- 

Ingolf Steinbach                       Jena-Optronik GmbH
address@hidden       ++49 3641 200-147
PGP: 0x7B3B5661  213C 828E 0C92 16B5  05D0 4D5B A324 EC04




------------------------------

Message: 5
Date: Tue, 18 Apr 2006 21:04:56 -0600
From: Eric Blake <address@hidden>
Subject: Re: C99 strto* protos
To: "Derek R. Price" <address@hidden>
Cc: bug-cvs <address@hidden>, "Mark D. Baushke" <address@hidden>,
        Paul Eggert <address@hidden>, address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Derek R. Price on 4/11/2006 8:48 AM:

> No one has objected in about a week and this patch plus a small typo
fix
> in m4/full-header-path.m4 is passing CVS nightly testing on some dozen
> platforms, so I committed it to GNULIB.

Sorry I haven't reviewed earlier.  In general, I like the idea of the
patch; some nitpicks below.

> 2006-04-11  Derek Price  <address@hidden>
>             Paul Eggert  <address@hidden>
> 
>         * lib/inttypes.h: New file.
>         * lib/strtoimax.c: Assume <inttypes.h>.
>         * m4/_inttypes_h.m4, m4/full-header-path.m4, m4/include_next:
New
>         files.
>         * modules/inttypes: New file.
>         * modules/strtoimax, modules/strtoumax: Depend on inttypes.
> 
+++ lib/inttypes.h      11 Apr 2006 14:27:29 -0000
+ *
+ * Currently, if the system <inttypes.h> is missing or not C99
compliant,
then
+ * this header may only to provide the required <stdint.h> (which may
be the

Grammar, fix by s/only to/just/.

+++ m4/_inttypes_h.m4   11 Apr 2006 14:27:29 -0000
@@ -0,0 +1,13 @@
+# _inttypes_h.m4 serial 1

Why does this file need a leading underscore in its name?  Nothing else
in
the m4 directory has one.

+++ m4/full-header-path.m4      11 Apr 2006 14:27:29 -0000
+# gl_FULL_HEADER_PATH(HEADER1 HEADER2 ...)
+# ----------------------------------------
+# Find the full path to a header file, when the #include_next directive
+# doesn't work and the header exists in the first place.  If the header
were
+# sys/inttypes.h (and it existed and #include_next didn't work), this
macro
+# would define FULL_PATH_SYS_INTTYPES_H to the quoted full path to
+# sys/inttypes.h in config.h
+# (e.g. `#define FULL_PATH_SYS_INTTYPES_H
"/usr/include/sys/inttypes.h"').
...
+  AC_CACHE_CHECK([full path to
<]m4_quote(m4_defn([gl_HEADER_NAME]))[>],

Do we want "" or <> quoting for FULL_PATH_*_H?  Probably <>, so the
documentation is wrong.

AC_DEFINE_UNQUOTED([FULL_PATH_]m4_quote(translit(m4_defn([gl_HEADER_NAME
]),
+
[-./abcdefghijklmnopqrstuvwxyz],

Should we make this rely on $as_cr_letters and friends, to make this
shorter?

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFERajY84KuGfSFAYARAjR1AJsHxjFhZec6t4iQk14IYyC+BCt2VQCgt6cW
vGRd2yQCKMmSUkSmtfpaX2Q=
=cdLQ
-----END PGP SIGNATURE-----




------------------------------

_______________________________________________
Bug-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/bug-cvs

End of Bug-cvs Digest, Vol 27, Issue 9
**************************************

This email may contain confidential or privileged information for the 
intended recipient(s) and the views expressed in the same are not 
necessarily the views of Zensar Technologies Ltd. If you are not the intended 
recipient or have received this e-mail by error, its use is strictly 
prohibited, please delete the e-mail and notify the sender. Zensar 
Technologies Ltd. does not accept any liability for virus infected mails.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]